Thank you Gregor for the links.
We are trying not to modify the Tomcat code at this point to avoid
regression testing. We decided to change our Tomcat startup scripts to
check for port issues and restart the server since this is the least
intrusive change at this point in our release cycle.
Thank
Thank you Gregor for the suggestion.
I was trying to see if there is a way to do this from within my
application code which is running under Tomcat. The issue is that I
don't have direct control over the scripts that start Tomcat.
Thanks
Shaji
-Original Message-
From: Gregor Schneider [
When Tomcat 6 finds that the specified AJP port is already in use, it
increments the port number and try to bind to the next available port. When
this happens, on the web server side apache is not able to connect to the AJP
port on Tomcat side, because Tomcat is listening on a different AJP port