Details

      Description

      This issue happens after https://issues.liferay.com/browse/LPS-51714
      When a node is started, it should retrieve the indexes from other node in the cluster.
      As the portal has not received any request yet at that point, the port should be established from the property portal.instance.http.protocol

      STEPS TO REPRODUCE
      1.- Set up in cluster two Liferay nodes
      2.- Include in portal-ext.properties for each node:

      browser.launcher.url=
      cluster.executor.debug.enabled=true
      portal.instance.protocol=http
      portal.instance.http.port=<HTTP-APP-SERVER-PORT> (usually 8080 and 9080 if you are setting up the cluster in the same machine)
      

      3.- Include in WEB-INF/classes/log4j.properties:

      log4j.logger.com.liferay.portal.search.lucene.LuceneHelperImpl=DEBUG
      log4j.logger.com.liferay.portal.search.lucene.IndexAccessorImpl=DEBUG
      

      4.- Start first node
      5.- Start second node

      EXPECTED RESULT
      In the node that you start you should see:

      09:03:16,011 INFO  [CLUSTER_EXECUTOR_CALLBACK_THREAD_POOL-1][LuceneHelperImpl:1158] Start loading lucene index files from cluster node mbp-de-sergio-4-39587
      09:03:32,432 DEBUG [CLUSTER_EXECUTOR_CALLBACK_THREAD_POOL-1][IndexAccessorImpl:363] Lucene store type file
      09:03:32,525 INFO  [CLUSTER_EXECUTOR_CALLBACK_THREAD_POOL-1][LuceneHelperImpl:1172] Lucene index files loaded successfully
      

      ACTUAL
      In the node that you start you see, port set with value -1:

      08:20:36,740 DEBUG [RuntimePageImpl-3][IndexAccessorImpl:211] Lucene store type file
      08:20:36,786 DEBUG [CLUSTER_EXECUTOR_CALLBACK_THREAD_POOL-1][LuceneHelperImpl:1145] Cluster node {clusterNodeId=7a367ff5-9dec-4f17-8fc9-f44526f3e0bc, portalProtocol=, inetAddress=/192.168.40.202, port=-1} has invalid port
      

      WORKAROUND
      There is a workaround for this problem and the port can be correctly set from properties if the HTTP and HTTPS port are set to the same value

      portal.instance.http.port=8080
      portal.instance.https.port=8080
      

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  4 years, 7 weeks ago

                  Packages

                  Version Package
                  6.1.X EE
                  6.2.4 CE GA5
                  6.2.X EE