-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when running liferay portal 6.2.5-ga6 #74
Comments
according to the LSP, there is a later version of 6.2.x that addresses this issue if you are tied to the ga6 docker image then perhaps you can use that as a base image and install a lower dist of jdk8? or you can try and patch the portal to the version on the LPS Portal ee-6.2.x GIT ID: 53ae89c814060cdeaee44210ec6a803efc362d5c. |
Thank you very much for your reply! That is much appreciated. And apologies for only getting back to you now. I have tried using the latest Docker images for both Liferay 6.2.5 (liferay/portal:6.2.5-ga6) and 6.2.10 (liferay/portal:6.2.10.21-sp20) versions. Both versions won't come up but rather throw the above mentioned exception. On that end I am a bit confused. How would I be able to use a later version of 6.2.x if both Docker 6.2.x images are not working? Also, is there a rational for releasing images that cannot be run out of the box? My workaround so far was to stick to an older explicit ga6 Docker image tag (liferay/portal:6.2.5-ga6-d1.3.0-20201215232311 to be precise). This workaround is basically using "a lower dist of jdk8" as this includes jdk1.8.0_232. Could you maybe please point me to where I could find the mentioned Git commit? I cannot find that ID anywhere within Github. I assume it must be in another repo somewhere. The LSP unfortunately doesn't link to it either. My fear currently is that this was fixed in the EE version only and not ported to the CE version. Many thanks for your support! |
Any update? |
Hello everybody, I created a file
Then I started the liferay server with
The mounted file will modify the java.version system property after startup to a patch version 255 that will be parsable by ICU4J. This solution works for 6.2.5-ga6 as well. Regards, |
Yes, I found same stackoverflow issue, too. But I use another way is download older java package from and use dockerfile copy into container, below is my dockerfile ARG LR_VERSION
FROM liferay/portal:${LR_VERSION}
COPY zulu8.46.0.19-ca-jdk8.0.252-linux_amd64.deb /zulu8.46.0.19-ca-jdk8.0.252-linux_amd64.deb
USER root
# RUN apt-get update && apt-get -y dist-upgrade
RUN apt -y --allow-downgrades install /zulu8.46.0.19-ca-jdk8.0.252-linux_amd64.deb |
When pulling and running the latest image liferay/portal:6.2.5-ga6 the portal will not work and print an error in the logs (note: the container is not stopping or crashing either):
After searching the web it seems that this is a known issue:
and related to the ICU4j library and/or the JVM minor version being greater than 255.
Any help or hints would be much appreciated.
The text was updated successfully, but these errors were encountered: