Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
Support for IBM J9 JDK
Is this a supported JDK or not? I posted an issue with the IBM J9 JDK here but nothing but crickets on the post. The Eclipse/OpenJ9 team is looking into it but they would also like to know what the Liferay team is doing to resolve any issues with the JDK. I found another issue with the the Liferay JSONSerializer and the J9 JDK as well but since it doesn't generate a stack trace, I haven't been able to post any details. Basically, when you use the JSONSerializer with the J9 JDK, you get nothing in return. It is a hassle to switch JDK's and rebuild but if a test project is needed, I guess I could create it.
Just wondering how much testing has been done with non-Oracle JDKs. I am running LR 7 CE GA5. How should JDK issues be reported?
Just wondering how much testing has been done with non-Oracle JDKs. I am running LR 7 CE GA5. How should JDK issues be reported?
Liferay tests running the portal under alternate JVMs, including IBM's which is necessary when running under websphere.
That said, they make no effort to ensure the build chain works on alternate JVMs. If you want to go all in, you're likely to be on your own and working with other IBM jvm adoptees.
Based on the dump in the other message, I wouldn't even know how to begin diagnosing what is going on there because you're missing key information such as a stack trace.
Besides, a segmentation fault typically results from a process failure, not a java code failure. So it looks like the ibm java process died on its own, and may not be related to the code itself.
That said, they make no effort to ensure the build chain works on alternate JVMs. If you want to go all in, you're likely to be on your own and working with other IBM jvm adoptees.
Based on the dump in the other message, I wouldn't even know how to begin diagnosing what is going on there because you're missing key information such as a stack trace.
Besides, a segmentation fault typically results from a process failure, not a java code failure. So it looks like the ibm java process died on its own, and may not be related to the code itself.
Hmmm...I hoped supported meant well tested. I kind of figured that I might be on my own here. The Open J9 team is looking into it but I'd like to give them more to help them out. Because the SASS issue with IBM JDK is a "known" issue with LR I assumed that the LR dev team would know what caused the issue rather than it just doesn't work with the IBM JDK. FWIW the support thread on the OpenJ9 Issues tracker is https://github.com/eclipse/openj9/issues/5961
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™