You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/03/22 08:03:47 UTC
DO NOT REPLY [Bug 27829] New: -
server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27829>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27829
server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable
Summary: server diying after: SEVERE: Caught exception trying to
unlock accept.\njava.net.SocketException: Network is
unreachable
Product: Tomcat 4
Version: 4.1.27
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: hauser@acm.org
even if there is a temporary network problem, I don't see why tomcat should
shutdown totally?
GlobalResourcesLifecycleListener: Destroying MBeans for Global JNDI Resources
Stopping service Privasphere-Standalone
Mar 21, 2004 9:22:02 PM org.apache.tomcat.util.net.PoolTcpEndpoint closeServerSocket
SEVERE: Caught exception trying to unlock accept.
java.net.SocketException: Network is unreachable
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.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:124)
at org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcp\
Endpoint.java:326)
at org.apache.tomcat.util.net.PoolTcpEndpoint.stopEndpoint(PoolTcpEndpo\
int.java:316)
at org.apache.coyote.http11.Http11Protocol.destroy(Http11Protocol.java:\
170)
at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:\
1205)
at org.apache.catalina.core.StandardService.stop(StandardService.java:5\
46)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:222\
5)
at org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catali\
na.java:624)
FATAL [Thread-1] (MyServlet.java:242) - Mar 21, 2004 9:22:03 PM: shutting down
MyServlet?
Stopping service Privasphere-Port8080
HttpConnector[8080] Stopping background thread
EngineConfig: EngineConfig: Processing STOP
HostConfig[www.privasphere.com]: HostConfig: Processing STOP
HostConfig[www.privasphere.com]: Undeploying deployed web applications
HostConfig[www.privasphere.com]: Undeploying web application at context path
StandardHost[www.privasphere.com]: Removing web application at context path
StandardContext[]: Stopping
StandardContext[]: Stopping filters
StandardContext[]: Sending application stop events
StandardContext[]: Processing standard container shutdown
ContextConfig[]: ContextConfig: Processing STOP
StandardContext[]: Stopping complete
Stopping service myApp
java.lang.Exception
at com.privasphere.myApp.MyServlet.destroy(MyServlet.java:235)
at org.apache.catalina.core.StandardWrapper.unload(StandardWrapper.java\
:1124)
at org.apache.catalina.core.StandardWrapper.unload(StandardWrapper.java\
:1124)
at org.apache.catalina.core.StandardWrapper.stop(StandardWrapper.java:1\
356)
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.jav\
a:1036)
at org.apache.catalina.startup.ContextConfig.stop(ContextConfig.java:70\
1)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConf\
ig.java:245)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecyc\
leSupport.java:166)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3\
676)
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.jav\
a:1036)
at org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDep\
loyer.java:470)
at org.apache.catalina.core.StandardHost.remove(StandardHost.java:852)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:\
758)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:\
758)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:738)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.jav\
a:360)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecyc\
leSupport.java:166)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1221)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233)
at org.apache.catalina.core.StandardService.stop(StandardService.java:5\
54)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:222\
5)
at org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catali\
na.java:624)
Is this a regression of Bug 344 ?
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: DO NOT REPLY [Bug 27829] New: -
server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable
Posted by MagicDraw Support Team <bu...@magicdraw.com>.
Hello bugzilla@apache.org:
Thank you for your inquiry. This is an automated response from MagicDraw support team. We have received
your message regarding "DO NOT REPLY [Bug 27829] New: -
server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable"
We would like to offer our sincere thanks to you for emailing us!
Your message has been recorded into our customer service database.
Our staff responds to messages during regular business hours European time,
although we also attempt to answer messages in the weekends whenever
possible. Messages are normally answered within one to two business days.
For even faster assistance, you can browse our FAQ list at:
http://www.magicdraw.com/faq.php
Sincerely,
MagicDraw Support Team
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org