You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by k9...@operamail.com on 2012/07/23 21:39:41 UTC
@ Tomcat 7.0.29 shutdown,
WARNING -> " Acceptor thread [null] failed to unlock. Forcing hard
socket shutdown". It the warning a problem, or ignorable?
I've Tomcat 7.0.29 installed on linux/64.
@ service shutdown,
sh /etc/init.d/tomcat7 stop
I see in my logs two "WARNING: Acceptor thread [null] failed to unlock.
Forcing hard socket shutdown":
INFO: Deploying web application directory
/usr/local/tomcat7/build/webapps/examples
Jul 23, 2012 11:18:35 AM
org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Jul 23, 2012 11:18:35 AM
org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Jul 23, 2012 11:18:35 AM
org.apache.catalina.core.ApplicationContext log
INFO: ContextListener:
attributeAdded('org.apache.jasper.compiler.TldLocationsCache',
'org.apache.jasper.compiler.TldLocationsCache@14d6cc5e')
Jul 23, 2012 11:18:35 AM
org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory
/usr/local/tomcat7/build/webapps/ROOT
Jul 23, 2012 11:18:35 AM
org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory
/usr/local/tomcat7/build/webapps/host-manager
Jul 23, 2012 11:18:36 AM
org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory
/usr/local/tomcat7/build/webapps/manager
Jul 23, 2012 11:18:36 AM
org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory
/usr/local/tomcat7/build/webapps/docs
Jul 23, 2012 11:18:36 AM
org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-apr-8080"]
Jul 23, 2012 11:18:36 AM
org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-apr-8009"]
Jul 23, 2012 11:18:36 AM
org.apache.catalina.startup.Catalina start
INFO: Server startup in 743 ms
Jul 23, 2012 12:24:12 PM
org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-apr-8080"]
Jul 23, 2012 12:24:12 PM
org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-apr-8009"]
Jul 23, 2012 12:24:12 PM
org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Jul 23, 2012 12:24:12 PM
org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextDestroyed()
Jul 23, 2012 12:24:12 PM
org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextDestroyed()
Jul 23, 2012 12:24:12 PM
org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-apr-8080"]
===> Jul 23, 2012 12:24:22 PM
org.apache.tomcat.util.net.AprEndpoint stopInternal
WARNING: Acceptor thread [null] failed to unlock.
Forcing hard socket shutdown.
Jul 23, 2012 12:24:22 PM
org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["ajp-apr-8009"]
===> Jul 23, 2012 12:24:32 PM
org.apache.tomcat.util.net.AprEndpoint stopInternal
WARNING: Acceptor thread [null] failed to unlock.
Forcing hard socket shutdown.
Jul 23, 2012 12:24:32 PM
org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-apr-8080"]
Jul 23, 2012 12:24:32 PM
org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["ajp-apr-8009"]
I'm not sure how much weight to give these warnings.
Can/should they be ignored?
Or does their cause need to be hunted down and fixed?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org