Re: Software caused connection abort Error in Tomcat on AIX
Thanks. This is not observed on solaris or linux however. Any specific issue in the native implemenation on AIX or windows which causes accept() call to terminate abnormally and not return a socket handle? --- On Wed, 3/10/10, Konstantin Kolinko wrote: > From: Konstantin Kolinko > Subject: Re: Software caused connection abort Error in Tomcat on AIX > To: "Tomcat Users List" > Date: Wednesday, March 10, 2010, 6:03 PM > 2010/3/10 Sharanabasavaraj Mudgal > : > > Hi! > > > > I am running tomcat 6.0.20 on AIX with > Tomcat-native(1.1.16) enabled. I get the following > exception during Tomcat Shutdown. > > > > SEVERE: Socket accept failed > > Throwable occurred: org.apache.tomcat.jni.Error: > Software caused connection abort > > at org.apache.tomcat.jni.Socket.accept(Native Method) > > at > org.apache.tomcat.util.net.AprEndpoint$Acceptor.run(AprEndpoint.java:1128) > > at java.lang.Thread.run(Thread.java:736) > > > > There are quite a few cases where the Acceptor thread > raises the exception when the file descriptor limits are > reached/there is issue with the file descriptor limit. > It’s interesting that in our case this exception is > raised during shutdown. > > This message (at shutdown time) is nothing to worry about, > it is expected. > It occurs because Socket.accept() call (waiting for an > incoming > connection) is being aborted. Because the accept() call > terminates > abnormally and cannot return a socket handle, return from > the call is > performed via an exception (*.jni.Error is used here). That > is what > you are seeing. > > 6.0.26 and later will not log this error. > http://svn.apache.org/viewvc?view=revision&revision=918495 > > > also mentions this issue. > > Best regards, > Konstantin Kolinko > > -https://issues.apache.org/bugzilla/show_bug.cgi?id=48584 > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Software caused connection abort Error in Tomcat on AIX
2010/3/10 Sharanabasavaraj Mudgal : > Hi! > > I am running tomcat 6.0.20 on AIX with Tomcat-native(1.1.16) enabled. I get > the following exception during Tomcat Shutdown. > > SEVERE: Socket accept failed > Throwable occurred: org.apache.tomcat.jni.Error: Software caused connection > abort > at org.apache.tomcat.jni.Socket.accept(Native Method) > at org.apache.tomcat.util.net.AprEndpoint$Acceptor.run(AprEndpoint.java:1128) > at java.lang.Thread.run(Thread.java:736) > > There are quite a few cases where the Acceptor thread raises the exception > when the file descriptor limits are reached/there is issue with the file > descriptor limit. It’s interesting that in our case this exception is raised > during shutdown. This message (at shutdown time) is nothing to worry about, it is expected. It occurs because Socket.accept() call (waiting for an incoming connection) is being aborted. Because the accept() call terminates abnormally and cannot return a socket handle, return from the call is performed via an exception (*.jni.Error is used here). That is what you are seeing. 6.0.26 and later will not log this error. http://svn.apache.org/viewvc?view=revision&revision=918495 https://issues.apache.org/bugzilla/show_bug.cgi?id=48584 also mentions this issue. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Software caused connection abort Error in Tomcat on AIX
Hi! I am running tomcat 6.0.20 on AIX with Tomcat-native(1.1.16) enabled. I get the following exception during Tomcat Shutdown. SEVERE: Socket accept failed Throwable occurred: org.apache.tomcat.jni.Error: Software caused connection abort at org.apache.tomcat.jni.Socket.accept(Native Method) at org.apache.tomcat.util.net.AprEndpoint$Acceptor.run(AprEndpoint.java:1128) at java.lang.Thread.run(Thread.java:736) There are quite a few cases where the Acceptor thread raises the exception when the file descriptor limits are reached/there is issue with the file descriptor limit. It’s interesting that in our case this exception is raised during shutdown. Did search quite a bit on the net and mailing-list for similar issues but not quite successful. Tested by binding to a specific ip as weil with no luck. 1)can anyone point to conditions that can cause this error? 2)Any debug options that can be used for the native code? 3)What is the impact of this error? Functionally, there seems to be no issue but we get this in the logs on shutdown. Thanks in Advance for the help. Sharan. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
