You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by fachhoch <fa...@gmail.com> on 2014/07/21 19:48:25 UTC

error in logs and application got undeployed

I am running tomcat 7,  my application was undeployed  automtically, here is
the   output from logs.
I  enabled jmx listner.


Jun 01, 2014 6:17:15 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 49114 ms
Jul 21, 2014 11:19:17 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop
executeAcceptLoop
WARNING: RMI TCP Accept-10001: accept loop for
ServerSocket[addr=0.0.0.0/0.0.0.0,localport=10001] throws
java.net.SocketTimeoutException: Accept timed out
        at java.net.PlainSocketImpl.socketAccept(Native Method)
        at
java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
        at java.net.ServerSocket.implAccept(ServerSocket.java:530)
        at java.net.ServerSocket.accept(ServerSocket.java:498)
        at
sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:388)
        at
sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:360)
        at java.lang.Thread.run(Thread.java:744)

Jul 21, 2014 11:19:58 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop
executeAcceptLoop
WARNING: RMI TCP Accept-1099: accept loop for
ServerSocket[addr=0.0.0.0/0.0.0.0,localport=1099] throws
java.net.SocketTimeoutException: Accept timed out
        at java.net.PlainSocketImpl.socketAccept(Native Method)
        at
java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
        at java.net.ServerSocket.implAccept(ServerSocket.java:530)
        at java.net.ServerSocket.accept(ServerSocket.java:498)
        at
sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:388)
        at
sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:360)
        at java.lang.Thread.run(Thread.java:744)

Jul 21, 2014 11:20:02 AM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run
SEVERE: Socket accept failed
java.net.SocketTimeoutException: Accept timed out
        at java.net.PlainSocketImpl.socketAccept(Native Method)
        at
java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
        at java.net.ServerSocket.implAccept(ServerSocket.java:530)
        at java.net.ServerSocket.accept(ServerSocket.java:498)
        at
org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:60)
        at
org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:219)
        at java.lang.Thread.run(Thread.java:744)

Jul 21, 2014 11:20:02 AM org.apache.catalina.core.StandardServer await
SEVERE: StandardServer.await: accept:
java.net.SocketTimeoutException: Accept timed out
        at java.net.PlainSocketImpl.socketAccept(Native Method)
        at
java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
        at java.net.ServerSocket.implAccept(ServerSocket.java:530)
        at java.net.ServerSocket.accept(ServerSocket.java:498)
        at
org.apache.catalina.core.StandardServer.await(StandardServer.java:452)
        at org.apache.catalina.startup.Catalina.await(Catalina.java:778)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:724)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:456)

Jul 21, 2014 11:20:02 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
Jul 21, 2014 11:20:02 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-bio-8009"]
Jul 21, 2014 11:20:02 AM org.apache.catalina.core.StandardService
stopInternal
INFO: Stopping service Catalina



--
View this message in context: http://tomcat.10.x6.nabble.com/error-in-logs-and-application-got-undeployed-tp5020214.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: java.net.SocketTimeoutException: Accept timed out

Posted by André Warnier <aw...@ice-sa.com>.
fachhoch wrote:
> Any Ideas what is causing this exception?, Is this anything to  do with
> increase ulimit?
> 

Googling for "tcp accept state" seems to provide some info.
Googling for "java.net.SocketTimeoutException: Accept timed out" also works.

> 
> 
> 
> --
> View this message in context: http://tomcat.10.x6.nabble.com/error-in-logs-and-application-got-undeployed-tp5020214p5020244.html
> Sent from the Tomcat - User mailing list archive at Nabble.com.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: java.net.SocketTimeoutException: Accept timed out

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: fachhoch [mailto:fachhoch@gmail.com] 
> Subject: RE: java.net.SocketTimeoutException: Accept timed out

> proposed if for 6.0.x.     (  the bug was filed for version 6.0.xx  and a
> fix   was proposed but did not  commit the fix  in version 6.0...x )

It was committed in 6.0.42.

> it will be in 7.0.55 onwards  (does this mean fix will be available from 
> 7.0.55  version onwards? )

Yes.

> backported it to 7.0.x    (I cannot understand why?)

Fixes are first put into trunk (currently the 8.0.x level), then backported to other currently supported levels, newer ones first.  The progression was 8.0.10, then 7.0.55, then 6.0.42.  The bugzilla entry is not marked closed until the fix has been committed to all supported levels.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: java.net.SocketTimeoutException: Accept timed out

Posted by fachhoch <fa...@gmail.com>.
Thank you for trying to help, my confusion 

proposed if for 6.0.x.     (  the bug was filed for version 6.0.xx  and a
fix   was proposed but did not  commit the fix  in version 6.0...x )


it will be in 7.0.55 onwards  (does this mean fix will be available from 
7.0.55  version onwards? )


backported it to 7.0.x    (I cannot understand why?)


Sorry for me being a pain, appreciate all your help.






--
View this message in context: http://tomcat.10.x6.nabble.com/error-in-logs-and-application-got-undeployed-tp5020214p5020749.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: java.net.SocketTimeoutException: Accept timed out

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: fachhoch [mailto:fachhoch@gmail.com] 
> Subject: Re: java.net.SocketTimeoutException: Accept timed out

> I think my errror is similar to one error reported in 
> https://issues.apache.org/bugzilla/show_bug.cgi?id=56684

> I am using jdk 7 64-bit and tomcat 7.0.52, is this fixed in 7.0.55?
> Please advice tomcat 7.0.55 has fix for this issue?

If you read the bug report, it says this:

"The workaround and simple debug code was pretty simple so I have backported it to 7.0.x (it will be in 7.0.55 onwards) and proposed if for 6.0.x."

What part don't you understand?

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: java.net.SocketTimeoutException: Accept timed out

Posted by fachhoch <fa...@gmail.com>.
I think my errror is similar to one error reported in 
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684

I got the error after   50 days as mentioned in the bug, 

I am using jdk 7 64-bit and tomcat 7.0.52, is this fixed in 7.0.55?
Please advice tomcat 7.0.55 has fix for this issue?







--
View this message in context: http://tomcat.10.x6.nabble.com/error-in-logs-and-application-got-undeployed-tp5020214p5020746.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


java.net.SocketTimeoutException: Accept timed out

Posted by fachhoch <fa...@gmail.com>.
Any Ideas what is causing this exception?, Is this anything to  do with
increase ulimit?




--
View this message in context: http://tomcat.10.x6.nabble.com/error-in-logs-and-application-got-undeployed-tp5020214p5020244.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org