Bug 1031953 - ERROR Socket accept failed: java.net.SocketException on graceful server shutdown
ERROR Socket accept failed: java.net.SocketException on graceful server shutdown
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Rémy Maucherat
Radim Hatlapatka
Russell Dickenson
Depends On:
  Show dependency treegraph
Reported: 2013-11-19 03:52 EST by Jitka Kozana
Modified: 2014-10-25 08:37 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-08-12 09:03:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jitka Kozana 2013-11-19 03:52:27 EST
EAP 6.2.0.CR2. 
When shutting down the server, the following error was sometimes seen in the log:

[0m[31m01:16:17,783 ERROR [org.apache.tomcat.util] (ajp-/ JBWEB003012: Socket accept failed: java.net.SocketException: Resource temporarily unavailable (errno:11)
	at java.net.PlainSocketImpl.socketAccept(Native Method) [rt.jar:]
	at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398) [rt.jar:]
	at java.net.ServerSocket.implAccept(ServerSocket.java:528) [rt.jar:]
	at java.net.ServerSocket.accept(ServerSocket.java:496) [rt.jar:]
	at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:61) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
	at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:309) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
	at java.lang.Thread.run(Thread.java:722) [rt.jar:]

See the server log here:

Comment 2 Martin Velas 2014-08-12 09:03:50 EDT
Based on the information provided by Jitka and Petr that this problem has not occurred during 6.3.0.x testing.

Note You need to log in before you can comment on or make changes to this bug.