the problem you are having is because you didn't shutdown the java process.
invoking shutdown.sh when your tomcat instance has suffered a memoryleak
doesn't guarantee that it will stop, or how long it takes to stop it.
you must ensure the process is killed properly
Filip
Bryce Nesbitt wrote:
We have a Tomcat application, which binds to port 8080 and AJP 6135. At
3 am we restart this application (because of a memory leak). But
sometimes it is unable to bind to it's own port, and it just dies and
never starts. Naturally this causes unhappiness. The server.xml is:
<Connector port="6135" protocol="AJP/1.3"
enableLookups="false"
connectionTimeout="20000"
maxThreads="150"
minSpareThreads="25"
maxSpareThreads="75"
/>
<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />
And the Java exception we get is:
INFO: Starting Coyote HTTP/1.1 on http-8080
Nov 16, 2006 7:08:02 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3501 ms
Nov 16, 2006 7:08:02 AM org.apache.catalina.core.StandardServer await
SEVERE: StandardServer.await: create[7135]:
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
...
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
...
Nov 16, 2006 7:08:13 AM org.apache.coyote.http11.Http11BaseProtocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
We're using Fedora Core 5 (fc5), and the dtomcat5 startup script. Do we
have to wait at least 20 seconds to be sure the port is clear?
-- ---- Visit http://www.obviously.com/
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
