Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-86089

Initial startup liferay default page not accessible via net ip4 address

    Details

    • Type: Bug
    • Status: Closed
    • Resolution: Won't Fix
    • Affects Version/s: 7.1.0 CE GA1
    • Fix Version/s: None
    • Component/s: Portal Configuration
    • Labels:
      None
    • Story Points:
      0.25

      Description

      Installing Liferay/Tomcat Bundle 7.1.0 on various machines and testing the installation process for the various platforms (Debian 9).

      Using Postgres 10.5 and JDK 10.

      Using default Liferay deployed application.

      I have successfully installed one Liferay Portal several weeks ago. Successful in that the Liferay Portal can be accessed at the ip4 address.

      On testing the installation process again for a new clean machine utilizing the same Liferay/Tomcat/Postgres/JDK10 sources, catalina.out shows multiple Equinox ERROR messages. The first run of startup.sh in tomcat/bin creates liferay listeners but these are not accessible via the net ip4 address. The first such ERROR is:

      2018-10-07 03:54:42.574 INFO [main][HikariDataSource:107] HikariPool-2 - Start completed.
      2018-10-07 03:54:43.272 INFO [main][BundleStartStopLogger:35] STARTED org.eclipse.osgi_3.10.200.v20150831-0856 [0]
      2018-10-07 03:54:43.790 ERROR [Framework Event Dispatcher: Equinox Container: c08b78b6-e4c9-0018-1862-8258bc4aa9b7][com_liferay_util_taglib:97] FrameworkEvent ERROR
      org.osgi.framework.BundleException: Could not resolve module: com.liferay.util.taglib [2]_ [sanitized]

       

      A ps -ef | grep liferay shows:

      • postgres 12811 10969 0 15:57 ? 00:00:00 postgres: 10/main: liferay lportal 127.0.0.1(51402) idle
        postgres 12812 10969 0 15:57 ? 00:00:00 postgres: 10/main: liferay lportal 127.0.0.1(51404) idle
      • [sanitized]

      I have checked the Liferay Issues and Community Message Boards but all references are related to an application deployment context which is not the case here as I am using just the default application for testing.

      portal-ext.properties:

      • jdbc.default.driverClassName=org.postgresql.Driver
        jdbc.default.url=jdbc:postgresql://localhost:5432/lportal
        jdbc.default.username=liferay
        jdbc.default.password=dragon

      setenv.sh

      • CATALINA_OPTS="$CATALINA_OPTS -Dfile.encoding=UTF8 -Djava.net.preferIPv4Stack=true -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false -Duser.timezone=GMT -Xmx1024m -XX:MaxMetaspaceSize=512m"
        JAVA_HOME=/usr/lib/jvm/jdk-10.0.2

      I have attached the full catalina.out log.

       

      On further checking I have found that the successful installation was with JDK 8 and the current version is JDK 10.

      Does this imply Liferay/Tomcat Bundle 7.1.0 is incompatible with JDK 10?

       It's the user's fault again!  Failed to update PATH with java in setenv.sh

      Problem Resolved

       

        Attachments

          Activity

            People

            Assignee:
            lu.liu Lu Liu
            Reporter:
            greenlogician Leslie Charles Green
            Participants of an Issue:
            Recent user:
            Lu Liu
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since last comment:
              2 years, 19 weeks, 1 day ago

                Packages

                Version Package