So… I assume then that if I am running 5.3.3.31-SNAPSHOT which is what I am running on the test server, then it should fix that?
OK… Let’s do this (and write this) in real time…
Here are the catalina.x.log and catalina.out files for a fresh reboot which has been running for about 3 hours, with the following set up:
-Lucee 5.3.3.31-SNAPSHOT installed at /opt/tomcat/webapps/WEB-INF and no other instance installed anywhere
-Open JDK 10.0.0.2
catalina.2019-05-16.log (21.7 KB)
catalina.out (84.2 KB)
And here are the catalina.x.log and catalina.out files for a fresh reboot of the following set up:
-Lucee 5.3.3.31-SNAPSHOT installed at /opt/tomcat/webapps/WEB-INF and no other instance installed anywhere
-Open JDK 11.0.1 (11+28)
catalina-11 28.out (10.0 KB)
catalina.2019-05-16-11 28.log (9.2 KB)
HOLY CRAP!
That actually appears to be working!
Since the production app is not mission critical and isn’t used after 5 PM, lemme go try that…
2 Likes
Woah! OK, this seems to be the (or, “a”) solution!!! Thank you! I actually DID see that LDEV thread earlier but it did not appear to be something I could use because I am not good at all about understanding the various catalina/java log errors. There is so much output and so many SEVERE errors that I simply didn’t know what to look for. That’s… my failing.
It appears that downgrading to Open JDK 11.0.1 will resolve the issue.
I don’t have luck with just changing the Lucee version, as I tried 5.3.3.31-SNAPSHOT and it did not like Open JDK 11.0.2 nor Open JDK 12, however I did not specifically try 5.3.3.23-SNAPSHOT, so maybe that one would work? Dunno.
Production is still running Lucee 5.1.3.102, so I switched the Open JDK from 10.0.0.2 to 11.0.1 (11+28) and all appears to be working well! And if not, it only takes a moment to go back to 10.0.0.2 now.
So, seems like moving back to Open JDK 11.0.1 (11+28) is a good solution as it gives you version 11 regardless of Lucee and things appear to be working normally so far.
Two days of my life more or less well spent since it resulted in an overall improvement in the environment.
Thank you for the comment and specifically asking the question!
1 Like
Awesome news, glad you got it worked out 
Stack traces are definitely not fun to read when you get down into much lower level stuff that you feel like you have no control over!
I guess this will continue to be a problem for Lucee 5.1.3.102 until there is a JDK fix (if at all), and a Java downgrade to 11.0.1 is less than ideal but at least we know it works.
If you did have the energy (another day) to test 5.3.3.23-SNAPSHOT (plus the very latest snapshot) while running Java 11.0.2 or 11.0.3 then that might help… The newer version of Felix in that build is also supposed to work around the JDK 11.0.2 issue which means instead of downgrading then we can just roll forward with newer Java 11 updates. We’d want to make sure this is fixed before the Lucee 5.3.3 release (if it isn’t already).
1 Like
OK. Here you go - zipped log files attached.
Combos in the log files (4 combos, 8 log files):
Lucee 5.3.3.23-SNAPSHOT and Open JDK 11.0.1 - WORKS as expect
Lucee 5.3.3.31-SNAPSHOT and Open JDK 11.0.1 - WORKS as expect
Lucee 5.3.3.23-SNAPSHOT and Open JDK 11.0.2 - jrt, memory leak, one context only
Lucee 5.3.3.31-SNAPSHOT and Open JDK 11.0.2 - jrt, memory leak, one context only
Prior test (no log file)
Lucee 5.3.3.31-SNAPSHOT and Open JDK 12.0.1 - jrt, memory leak, one context only
And of course I know that
Lucee 5.3.1.102 and Open JDK 11.0.1 -WORKS as expected
Lucee 5.3.1.102 and Open JDK 11.0.2 - jrt, memory leak, one context only
Lucee 5.3.1.102 and Open JDK 12.0.1 - jrt, memory leak, one context only
Additional update: Just tried 11.0.3 and Lucee 5.3.3.39 snapshot - jrt, memory leak, one context only
Same error:
java.lang.IllegalStateException: Unknown protocol: jrt
test-5-3-3-23-snap-jdk-11-0-2-logs.zip (32.5 KB)
1 Like
Ubuntu Software Center, and click on history
see the updates, uninstall the updates.
I recommend RHEL/CENTOS for production over Ubtunu
Hey! Sunny Day! I’ve just tested Lucee 5.3.3.60-RC and OpenJDK 12.0.1 and it works as it should. Can run multiple contexts and Tomcat admin. No more JRT error! Thanks - to everyone who fixed this!
4 Likes