Severe critical error during deployment with Tomcat 9.0.87
Description
Attachments
is related to
Activity
Julian Janetschek June 20, 2024 at 7:38 AM
FYI: I have deployed a instance of the latest s2u-22.x branch with tomcat 9.0.89 and the same error does occur. But the fix from does resolve the issue.
Sean Horner April 16, 2024 at 6:14 PM
I’ll close this issue as ‘can’t reproduce', though others are certainly welcome to revert that in order to track this issue further.
Julian Janetschek April 16, 2024 at 3:14 PM
Yes, merging the latest code does resolve the issue for me.
Sean Horner April 15, 2024 at 9:21 PM
I think this issue is actually hinging on the state of the Sakai source code deployed. Back in March 22 when I reported this issue, both 23.x and 25.x exhibited the problem. Using current /latest versions of the source code (same JAVA_OPTS), the issue does not occur for either version. If however I revert 25.x to before March 22 (d502aa7a1ccff4f0e224c514bc7bf5900910ec4c) then I can reproduce this bug.
Julian Janetschek April 15, 2024 at 8:42 AM
We are using -XX:+UseG1GC and also see the error
Details
Details
Priority
CriticalAffects versions
23 Status
Components
Assignee
Matthew JonesReporter
Sean Horner
A severe critical error (see attached log) is thrown for Sakai 23 and 25 when deployed with Tomcat 9.0.87. Downstream, accessing the Preferences tool will yield the Error screen and throw exceptions.
I surmise this may be a Tomcat bug and not a Sakai issue. This severe critical error does not manifest when Sakai is deployed with Tomcat 9.0.86. The temporary solution may be to revise the master/pom.xml file to refer to 9.0.86 until a future version of Tomcat does not induce
I have not tested Sakai 22 which may have this problem too, but Sakai 21 does not.