Jason,
On 3/19/25 1:53 PM, Jason Countryman wrote:
Hello,
I'm using Tomcat 10.1.34 on Debian Bookworm. I have a multiple CATALINA_HOME
one CATALINA_BASE configuration, which works perfectly, most of the time.
There are 4 CATALINA_HOME setups.
The issue is that one of these CATALINA_BASE setups, when getting the shutdown
command from the shutdown port, appears to shut down normally. Unfortunately,
it never appears to release the connector port for which it's configured. When
it's restarted, it fails as it's unable to bind to the port.
I've checked using netstat, lsof, ss, ps to see if there's anything else using
this port or if the java process for that tomcat instance still exists, with
no luck. The process is gone after the shutdown and nothing is using the port,
at least that linux can report. I'm wondering if there's an orphaned thread
from that instance, perhaps.
This instance uses a Spring configuration with log4j2, camel and cxf.
I'm not sure what the next troubleshooting step would be here, what to look
for. Any guidance on next steps would be appreciated.
Is the process still running? My guess is that the old process is never
actually stopping.
This can happen if you have non-daemon threads from your application
that refuse to stop.
Try taking a thread-dump after your shutdown attempt to see what's still
running.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
