Details

    • Type: Bug
    • Status: Closed
    • Resolution: No Longer Reproducible
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0
    • Component/s: Content Targeting
    • Labels:
      None
    • Fix Priority:
      4

      Description

      Steps to reproduce:

      1. Execute an upgrade from 6.2 to 7.0 using the attached database and data folder
      2. Set indexReadOnly=false in com.liferay.portal.search.configuration.IndexStatusManagerConfiguration.cfg
      3. Start up portal
      4. Deploy content targeting jars

      Expected result: Content Targeting upgrade process completes successfully
      Actual result: Exceptions are thrown during upgrade process

      Note: These errors are not reproducible in the following steps:

      1. Execute an upgrade from 6.2 to 7.0
      2. Leave indexReadOnly=true in com.liferay.portal.search.configuration.IndexStatusManagerConfiguration.cfg (no change from upgrade process)
      3. Start up portal
      4. Deploy content targeting jars

      Reproduced on:
      Tomcat 8.0.32 + MySQL 5.7
      Portal ee-7.0.x GIT ID: 3365bc9b5250db906ed5be98cadd38c464bcca85
      Content Targeting GIT ID: a5fb4a8b1078ef30ae4aa52cbef0776e310f44a1 (RC7)

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  2.0