Did you ever resolve the timeout problem? I started having the same symptom
with 5.0.27. Here is what's in my log
Oct 19, 2004 5:07:16 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8052
Oct 19, 2004 5:10:25 PM org.apache.coyote.tomcat5.CoyoteConnector pause
SEVERE: Protocol handler pause failed
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:153)
at
org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:460)
at org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:272)
at org.apache.jk.server.JkMain.pause(JkMain.java:657)
at
org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:202)
at
org.apache.coyote.tomcat5.CoyoteConnector.pause(CoyoteConnector.java:1444)
at
org.apache.catalina.core.StandardService.stop(StandardService.java:521)
at
org.apache.catalina.core.StandardServer.stop(StandardServer.java:2347)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:605)
at org.apache.catalina.startup.Catalina.start(Catalina.java:580)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:284)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422)
Oct 19, 2004 5:10:26 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Agent8050
Oct 19, 2004 5:10:26 PM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /example
Oct 19, 2004 5:10:26 PM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /manager
Oct 19, 2004 5:10:26 PM org.apache.catalina.logger.LoggerBase stop
INFO: unregistering logger Agent8050:type=Logger
Oct 19, 2004 5:10:26 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8052
Oct 19, 2004 5:10:28 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8052
Oct 19, 2004 5:10:28 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1116 ms
Oct 19, 2004 5:10:28 PM org.apache.catalina.realm.JAASRealm setContainer
INFO: Setting JAAS app name Agent8050
Oct 19, 2004 5:10:28 PM org.apache.catalina.core.StandardService start
INFO: Starting service Agent8050
Oct 19, 2004 5:10:28 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.27
Oct 19, 2004 5:10:28 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Oct 19, 2004 5:10:28 PM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Oct 19, 2004 5:10:28 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Processing Context configuration file URL
file:/www/tmc/tomcat5.0.27/c8050/conf/Agent8050/localhost/manager.xml
Oct 19, 2004 5:10:28 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Processing Context configuration file URL
file:/www/tmc/tomcat5.0.27/c8050/conf/Agent8050/localhost/example.xml
Oct 19, 2004 5:10:28 PM org.apache.catalina.startup.ContextConfig
applicationConfig
INFO: Missing application web.xml, using defaults only
StandardEngine[Agent8050].StandardHost[localhost].StandardContext[/example]
Oct 19, 2004 5:10:29 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8052
Oct 19, 2004 5:10:29 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8051
Oct 19, 2004 5:10:29 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/42 config=null
Oct 19, 2004 5:10:29 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1071 ms
Not sure why it seems to start back up.
This is my server.xml file.
<Server port="8050" shutdown="SHUTDOWN" debug="0">
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>
<GlobalNamingResources>
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>
<Service name="Agent8050">
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
<Connector port="8052"
maxThreads="50" minSpareThreads="4" maxSpareThreads="25"
enableLookups="false" redirectPort="8443" acceptCount="100"
debug="0" connectionTimeout="20000"
disableUploadTimeout="true" />
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<Connector port="8051"
enableLookups="false" redirectPort="8443" debug="0"
protocol="AJP/1.3" />
<Engine name="Agent8050" defaultHost="localhost" debug="0"
jvmRoute="nss">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="Agent8050." suffix=".log"
timestamp="true"/>
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0"
saveOnRestart="true"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1">
<Store
className="org.apache.catalina.session.FileStore"/>
</Manager>
<Host name="localhost" debug="0" appBase="webapps"
unpackWARs="false" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
</Host>
</Engine>
</Service>
</Server>
I have deployed what should be identical installs on SuSE 8.2 Pro and SuSE
Enterprise 8 (SLES8). The connection timeout occurs only on SLES8.
Any help would be appreciated.
Paul
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 21, 2004 4:45 AM
To: Tomcat Users List
Subject: RE: shutdown problems tomcat 5.0.28
Thanks for the advice. I have tried a number of new things with no
success.
1. I removed the JNDI configuration file for my application.
2. I verified that port 8005 is listed in the server.xml file. I also did
"netstat -a | grep 8005" and verified that the port is open and listening
when tomcat is running. And I can telnet to that port as localhost when
tomcat is running with no problems.
3. I verified that I had all the required jar files as listed in the
release notes.
4. The release notes mention changing the default stack size for Linux
users. I did that, "ulimit -s 2048".
5. The release notes also mention setting an environment variable called
LD_ASSUME_KERNEL. I set that to the value suggested in the release notes:
2.2.5
After each change I would start and then stop tomcat and still tomcat
hangs, then reports exceptions in the catalina.out, before finally stopping
after about 5 minutes.
Sep 21, 2004 5:35:21 AM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Sep 21, 2004 5:38:30 AM org.apache.coyote.tomcat5.CoyoteConnector pause
SEVERE: Protocol handler pause failed
java.net.ConnectException: Connection timed out
etc...
Has anyone else had a problem like this?
"Shapira, Yoav"
<[EMAIL PROTECTED] To: "Tomcat Users List"
<[EMAIL PROTECTED]>
i.com> cc:
Subject: RE: shutdown
problems tomcat 5.0.28
09/20/04 06:15
PM
Please respond
to "Tomcat Users
List"
Hi,
If you remove your separate JNDI configurations file, does the problem
go away?
Can you verify the shutdown socket (8005 by default) is open and
listening (use a program like netstat to do this)?
Have you tried setting the LD_ASSUME_KERNEL parameter that many Linux
users suggest on RedHat> (search the archives of this list for
LD_ASSUME_KERNEL) for details)
Yoav Shapira
Millennium Research Informatics
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: Monday, September 20, 2004 11:52 AM
>To: [EMAIL PROTECTED]
>Subject: shutdown problems tomcat 5.0.28
>
>I am running tomcat 5.0.28 on Redhat 9.0 with java 1.4.2_05.
>
>Starting tomcat using startup.sh shows no errors in any of the log
files.
>The application is running fine. However, when I use shutdown.sh,
tomcat
>hangs for a few minutes, prints the below message in catalina.out, and
>finally exits. Obviously, I can kill the process using the kill
command
>but I am afraid that this problem might be a symptom of a larger
problem.
>
>The server.xml file is the default that came with the release. All
JNDI
>configurations are done in a separate context file that lives in
>$TOMCAT/conf//Catalina/localhost/.
>
>I have found some similar posts on the net but none seem to address my
>problem sufficiently. Any advice on how to debug this would be
>appreciated.
>
>Here is the Catalina.out error:
>
>Sep 20, 2004 12:44:28 PM org.apache.coyote.http11.Http11Protocol pause
>INFO: Pausing Coyote HTTP/1.1 on http-8080
>Sep 20, 2004 12:47:37 PM org.apache.coyote.tomcat5.CoyoteConnector
pause
>SEVERE: Protocol handler pause failed
>java.net.ConnectException: Connection timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential,
proprietary and/or privileged. This e-mail is intended only for the
individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else. If you are not the(an) intended
recipient, please immediately delete this e-mail from your computer system
and notify the sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains information of
Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or
its affiliates (which may be known outside the United States as Merck Frosst, Merck
Sharp & Dohme or MSD and in Japan, as Banyu) that may be confidential, proprietary
copyrighted and/or legally privileged. It is intended solely for the use of the
individual or entity named on this message. If you are not the intended recipient,
and have received this message in error, please notify us immediately by reply e-mail
and then delete it from your system.
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
