PUBLIC - Liferay Portal Community Edition
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-32722

Virtual host settings lost during upgrade to 6.2 with Oracle database

    Details

    • Branch Version/s:
      6.1.x
    • Backported to Branch:
      Committed
    • Story Points:
      9
    • Fix Priority:
      5
    • Where was the bug?:
      Java
    • Similar Issues:
      Show 4 results 

      Description

      When upgrading form 6.0.11 to 6.1.20 the virtual host setting were not migrated.

      1) company virtual host was stored in "Company" table in "virtualhost" field
      2) site's/organization's virtual host was stored in "LayoutSet" table in "virtualhost" field

      In 6.1.20 virtual hosts are stored in the VIRTUALHOST table, but neither of the above settings were migrated to the new place.

      After upgrade when accessing the Portal Settings portlet in the ControlPanel, the attached exception is thrown. The company virtual host field is required but it cannot be found.

      Reproduction steps:

      1) start a 6.0.11 portal with oracle
      2) set virtual host
      3) upgrade to 6.1.20
      4) Go to Control Panel -> Portal Instances -> click on the virtual host:
      jodd.bean.BeanException: Simple property not found: hostname Invalid property: 'CompanyImpl#hostname' (actual:'CompanyImpl#hostname', forced=false)

        Issue Links

          Activity

          Hide
          Pani Gui (Inactive) added a comment -

          FAILED Manual Testing following the steps in the description.

          Reproduced on:
          Tomcat 7.0 + Oracle 11. Portal 6.1.20 EE GA2.

          The virtual host added in Portal Instances is lost after upgrading.

          Failed on:
          Tomcat 7.0 + Oracle 11. Portal 6.1.x EE GIT ID: 81bf916b461b5475b17faf4c56660632c79b696a.
          Tomcat 7.0 + Oracle 11. Portal 6.2.x GIT ID: 9ec2631b9cd9c9e1cfc57db16c454be2a52e52de.

          The virtual host does not display in Portal Instances.

          Show
          Pani Gui (Inactive) added a comment - FAILED Manual Testing following the steps in the description. Reproduced on: Tomcat 7.0 + Oracle 11. Portal 6.1.20 EE GA2. The virtual host added in Portal Instances is lost after upgrading. Failed on: Tomcat 7.0 + Oracle 11. Portal 6.1.x EE GIT ID: 81bf916b461b5475b17faf4c56660632c79b696a. Tomcat 7.0 + Oracle 11. Portal 6.2.x GIT ID: 9ec2631b9cd9c9e1cfc57db16c454be2a52e52de. The virtual host does not display in Portal Instances.
          Hide
          Pani Gui (Inactive) added a comment -

          FAILED Manual Testing following the steps in the description.

          Reproduced on:
          Tomcat 7.0 + Oracle 11. Portal 6.1.20 EE GA2.

          The virtual host added in Portal Instances is lost after upgrading.

          Fixed on:
          Tomcat 7.0 + Oracle 11. Portal 6.2.x GIT ID: 1461c78e5932a636946b7e3cb4381f96b8eb3cfb.

          The virtual host displays properly.

          Failed on:
          Tomcat 7.0 + Oracle 11. Portal 6.1.x EE GIT ID: c6e6bbe09d1ad713991053ca79fbd28f5161b2cc.

          The virtual host does not display in Portal Instances.

          Show
          Pani Gui (Inactive) added a comment - FAILED Manual Testing following the steps in the description. Reproduced on: Tomcat 7.0 + Oracle 11. Portal 6.1.20 EE GA2. The virtual host added in Portal Instances is lost after upgrading. Fixed on: Tomcat 7.0 + Oracle 11. Portal 6.2.x GIT ID: 1461c78e5932a636946b7e3cb4381f96b8eb3cfb. The virtual host displays properly. Failed on: Tomcat 7.0 + Oracle 11. Portal 6.1.x EE GIT ID: c6e6bbe09d1ad713991053ca79fbd28f5161b2cc. The virtual host does not display in Portal Instances.
          Hide
          Laszlo Csontos added a comment -

          Hi Pani,

          Could you please check table virtualhost in the database whether it contains those hosts?

          Thanks,
          László.

          Show
          Laszlo Csontos added a comment - Hi Pani, Could you please check table virtualhost in the database whether it contains those hosts? Thanks, László.
          Hide
          Laszlo Csontos added a comment -

          Further discussing the issue with Pani, we've just found out the following.

          Upon upgrading from 6.0.12 EE to 6.1.x EE, the upgrade process is defined in the following way.

          upgrade.processes.6011=\
                  com.liferay.portal.upgrade.UpgradeProcess_6_0_12\,\
                  com.liferay.portal.upgrade.UpgradeProcess_6_0_12_to_6_1_0\,\
                  com.liferay.portal.upgrade.UpgradeProcess_6_1_1
          
          upgrade.processes.6012=${upgrade.processes.6011}
          

          Unfortunately com.liferay.portal.upgrade.UpgradeProcess_6_0_12_to_6_1_0 differs from com.liferay.portal.upgrade.UpgradeProcess_6_1_0 in that that it doesn't contain - among others - UpgradeVirtualHost. So UpgradeVirtualHost doesn't even get executed and that's the reason of the experienced behaviour.

          Having this in mind this is rather an other issue related to the upgrade framework itself than a bug in UpgradeVirtualHost.

          The original issue can be tested manually when an upgrade is made from 6.0.10 EE to 6.1.x EE, because it does include com.liferay.portal.upgrade.UpgradeProcess_6_1_0 which in turn executes UpgradeVirtualHost.

          Show
          Laszlo Csontos added a comment - Further discussing the issue with Pani, we've just found out the following. Upon upgrading from 6.0.12 EE to 6.1.x EE , the upgrade process is defined in the following way. upgrade.processes.6011=\ com.liferay.portal.upgrade.UpgradeProcess_6_0_12\,\ com.liferay.portal.upgrade.UpgradeProcess_6_0_12_to_6_1_0\,\ com.liferay.portal.upgrade.UpgradeProcess_6_1_1 upgrade.processes.6012=${upgrade.processes.6011} Unfortunately com.liferay.portal.upgrade.UpgradeProcess_6_0_12_to_6_1_0 differs from com.liferay.portal.upgrade.UpgradeProcess_6_1_0 in that that it doesn't contain - among others - UpgradeVirtualHost . So UpgradeVirtualHost doesn't even get executed and that's the reason of the experienced behaviour. Having this in mind this is rather an other issue related to the upgrade framework itself than a bug in UpgradeVirtualHost . The original issue can be tested manually when an upgrade is made from 6.0.10 EE to 6.1.x EE , because it does include com.liferay.portal.upgrade.UpgradeProcess_6_1_0 which in turn executes UpgradeVirtualHost .
          Hide
          Pani Gui (Inactive) added a comment -

          PASSED Manual Testing following the steps in the description.

          Reproduced on:
          Tomcat 7.0 + Oracle 11. Portal 6.1.20 EE GA2.

          The virtual host added in Portal Instances is lost after upgrading.

          Fixed on:
          Tomcat 7.0 + Oracle 11. Portal 6.1.x EE GIT ID: 0ff32fbbf8504fbd089281ac0ed97759f95d6a5b.
          Tomcat 7.0 + Oracle 11. Portal 6.2.x GIT ID: 627c3e8369d32192e0e347ef85e7178dc5274fe3.

          Test Upgrade 6.0.10 to 6.1.x EE.
          Test Upgrade 6.0.6 to 6.2.x.

          The virtual host displays properly.

          Show
          Pani Gui (Inactive) added a comment - PASSED Manual Testing following the steps in the description. Reproduced on: Tomcat 7.0 + Oracle 11. Portal 6.1.20 EE GA2. The virtual host added in Portal Instances is lost after upgrading. Fixed on: Tomcat 7.0 + Oracle 11. Portal 6.1.x EE GIT ID: 0ff32fbbf8504fbd089281ac0ed97759f95d6a5b. Tomcat 7.0 + Oracle 11. Portal 6.2.x GIT ID: 627c3e8369d32192e0e347ef85e7178dc5274fe3. Test Upgrade 6.0.10 to 6.1.x EE. Test Upgrade 6.0.6 to 6.2.x. The virtual host displays properly.

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                1 year, 37 weeks, 6 days ago

                Development

                  Structure Helper Panel