Does anyone have any experience tracking what I think is a Tomcat issue?
Our staging server is on AWS - we’re using AWS Linux 2.
Anyway the issue I am facing is that the tomcat service “just” stops.
I have changed all the settings I can find in tomcat/conf/logging.properties to “FINE”
And uncommented the few that were commented out, too.
I have also changed the Lucee logging to trace for exception, application and requesttimeout logs.
All tomcat AND Lucee logs are un-remarkable - no real errors are logged;
I see in the requesttimeout.log;
"INFO","Thread-16","06/08/2022","13:08:38","controller","downgrade priority of the a request at path: /web/centra/wwwroot/index.cfm (/web/centra/cfmapping/coldspring/beans/BeanDefinition.cfc). Open locks at this time [bf_e9a16849-8ac0-456e-97d5ae85e0204f8a.bean_customerservice].;java.lang.Throwable;java.lang.Throwable
But the path / etc changes depending on where I am in the app at the time the tomcat Service stops.
We were using tomcat v 9.0.59, without issue.
And yesterday I upgraded to 9.0.63.
I have downgraded tomcat to 9.0.59 - and still the get error.
service tomcat status : shows;
Redirecting to /bin/systemctl status tomcat.service
● tomcat.service - Tomcat 9 servlet container
Loaded: loaded (/etc/systemd/system/tomcat.service; enabled; vendor preset: disabled)
Active: failed (Result: signal) since Wed 2022-06-08 14:14:14 AEST; 26s ago
Process: 6698 ExecStop=/usr/share/tomcat/current/bin/shutdown.sh (code=exited, status=0/SUCCESS)
Process: 6817 ExecStart=/usr/share/tomcat/current/bin/startup.sh (code=exited, status=0/SUCCESS)
Main PID: 6827 (code=killed, signal=KILL)
Jun 08 14:07:34 servername systemd: Starting Tomcat 9 servlet container…
Jun 08 14:07:34 servername startup.sh: Existing PID file found during start.
Jun 08 14:07:34 servername startup.sh: Removing/clearing stale PID file.
Jun 08 14:07:34 servername systemd: Started Tomcat 9 servlet container.
Jun 08 14:14:14 servername systemd: tomcat.service: main process exited, code=killed, status=9/KILL
Jun 08 14:14:14 servername systemd: Unit tomcat.service entered failed state.
Jun 08 14:14:14 servername systemd: tomcat.service failed.
After some googling I thought it might be related to “context” swapping.
I.e. - going from the app to Lucee Admin or vice-versa…
The issue happens in our app : without trying anything else,
and also in Lucee Admin without shifting to a different app / context
(After a service restart, for each)
Not being a Java developer, I have very little experience with Java containers and would appreciate any thoughts any one might have.
Lucee : 18.104.22.168
Java : OpenJDK 11.0.13
Tomcat : 9.0.59 AND 9.0.63
As always thanks!