Bug 972645 - HPUX natives: "No buffer space available" after server shutdown
HPUX natives: "No buffer space available" after server shutdown
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Apache Server (httpd) and Connectors (Show other bugs)
ia64 Other
unspecified Severity high
: DR1
: EAP 6.4.0
Assigned To: Jean-frederic Clere
Jan Stefl
Depends On:
  Show dependency treegraph
Reported: 2013-06-10 06:19 EDT by Jan Stefl
Modified: 2018-03-05 10:28 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
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 Jan Stefl 2013-06-10 06:19:47 EDT
 - I have installed and enabled natives with configured https, everything works as expected, but after server shutdown "No buffer space available" appears in log.

04:16:43,400 ERROR [org.apache.tomcat.util] (http-localhost.dxb.redhat.com/ JBWEB003012: Socket accept failed: org.apache.tomcat.jni.Error: No buffer space available
        at org.apache.tomcat.jni.Socket.accept(Native Method) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
        at org.apache.tomcat.util.net.AprEndpoint$Acceptor.run(AprEndpoint.java:1138) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
        at java.lang.Thread.run(Thread.java:722) [rt.jar:]

This is know issue, see [1]. Patch exists, but it is not applied on EAP's jbossweb.jar.

[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=50273
Comment 1 Mladen Turk 2013-06-10 06:27:07 EDT
Jean-Frederic can you take this issue.
Comment 2 Jean-frederic Clere 2013-06-10 08:00:44 EDT
fixed in JBossWeb by r2217.
Comment 6 Kabir Khan 2014-12-05 07:34:56 EST
This appears to have been done for 6.3.0, so I am setting it to ON_QA for 6.4.0
Comment 7 Jan Stefl 2014-12-15 06:41:23 EST
Verified in 6.4.0.DR13


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