QC failed to start, actual combat record _service

This morning QC also used well, the afternoon will suddenly not open, urgent, service restart again or not. Finally, the error message is truncated, carefully studied, but also thanks to the Friends of the test group to help, finally found some direction.

The following error message is posted:

Objectname:jboss.mq.destination:name=testtopic,service=topic
State:configured
I Depend on:
Jboss.mq:service=destinationmanager
Jboss.mq:service=securitymanager

Objectname:jboss.mq.destination:name=securedtopic,service=topic
State:configured
I Depend on:
Jboss.mq:service=destinationmanager
Jboss.mq:service=securitymanager

Objectname:jboss.mq.destination:name=testdurabletopic,service=topic
State:configured
I Depend on:
Jboss.mq:service=destinationmanager
Jboss.mq:service=securitymanager

Objectname:jboss.mq.destination:name=testqueue,service=queue
State:configured
I Depend on:
Jboss.mq:service=destinationmanager
Jboss.mq:service=securitymanager

Objectname:jboss.mq.destination:name=a,service=queue
State:configured
I Depend on:
Jboss.mq:service=destinationmanager

Objectname:jboss.mq.destination:name=b,service=queue
State:configured
I Depend on:
Jboss.mq:service=destinationmanager

Objectname:jboss.mq.destination:name=c,service=queue
State:configured
I Depend on:
Jboss.mq:service=destinationmanager

Objectname:jboss.mq.destination:name=d,service=queue
State:configured
I Depend on:
Jboss.mq:service=destinationmanager

Objectname:jboss.mq.destination:name=ex,service=queue
State:configured
I Depend on:
Jboss.mq:service=destinationmanager

Objectname:jboss.mq:service=invoker
State:configured
I Depend on:
Jboss.mq:service=tracinginterceptor
Depends on Me:
Jboss.mq:service=invocationlayer,type=http
Jboss.mq:service=invocationlayer,type=jvm
Jboss.mq:service=invocationlayer,type=uil2

Objectname:jboss.mq:service=tracinginterceptor
State:configured
I Depend on:
Jboss.mq:service=securitymanager
Depends on Me:
Jboss.mq:service=invoker

Objectname:jboss.mq:service=securitymanager
State:configured
I Depend on:
Jboss.mq:service=destinationmanager
Depends on Me:
Jboss.mq.destination:name=testtopic,service=topic
Jboss.mq.destination:name=securedtopic,service=topic
Jboss.mq.destination:name=testdurabletopic,service=topic
Jboss.mq.destination:name=testqueue,service=queue
Jboss.mq:service=tracinginterceptor
Jboss.mq.destination:name=dlq,service=queue

Objectname:jboss.mq.destination:name=dlq,service=queue
State:configured
I Depend on:
Jboss.mq:service=destinationmanager
Jboss.mq:service=securitymanager

Objectname:jboss.mq:service=invocationlayer,type=jvm
State:configured
I Depend on:
Jboss.mq:service=invoker

Objectname:jboss.mq:service=invocationlayer,type=uil2
State:configured
I Depend on:
Jboss.mq:service=invoker

Objectname:jboss.jmx:name=invoker,protocol=jrmp,service=proxyfactory,type=adapt
Or
State:configured
I Depend on:
Jboss:service=invoker,type=jrmp
Jboss.jmx:name=invoker,type=adaptor
Depends on Me:
Jboss.admin:service=pluginmanager

Objectname:jboss.jca:name=defaultds,service=datasourcebinding
State:configured
I Depend on:
jboss.jca:name=defaultds,service=localtxcm
Jboss:service=invoker,type=jrmp
Depends on Me:
Jboss.ejb:persistencepolicy=database,service=ejbtimerservice
Jboss:service=keygeneratorfactory,type=hilo
Jboss.mq:service=statemanager
Jboss.mq:service=persistencemanager

Objectname:jboss.web.deployment:id=-313524695,war=10sabin.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss.web.deployment:id=695086246,war=20qcbin.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss.web.deployment:id=522596599,war=jmx-console.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss.web.deployment:id=816467849,war=mtours.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

---mbeans that ARE the ROOT cause of the PROBLEM---
Objectname:jboss.web.deployment:id=456299907,war=root.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss.web.deployment:id=816467849,war=mtours.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss.web.deployment:id=-313524695,war=10sabin.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss.web.deployment:id=695086246,war=20qcbin.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss:service=naming
State:failed
Reason:java.rmi.server.ExportException:Listen failed on port:0; Nested EXCE
Ption is:
Java.net.SocketException:No buffer space available (maximum connections
Reached?): Listen failed
I Depend on:
Jboss.system:service=threadpool

Objectname:jboss.web.deployment:id=-1186264804,war=jbossmq-httpil.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss:service=webservice
State:failed
Reason:java.net.SocketException:No buffer space available (maximum Connectio
NS reached?): Listen failed
Depends on Me:
Jboss.ejb:service=ejbdeployer
Jboss.ws4ee:service=axisservice

Objectname:jboss.web.deployment:id=522596599,war=jmx-console.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss.web.deployment:id=-1203405164,war=invoker.war
State:failed
Reason:org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D Throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss.web.deployment:id=-1108639270,war=jboss-ws4ee.war
  state:failed
  Reason: Org.jboss.deployment.DeploymentException:Error during deploy; -Neste
D throwable: (Javax.naming.NameNotFoundException:comp not bound)

Objectname:jboss:service=invoker,type=jrmp
State:failed
Reason:java.rmi.server.ExportException:Listen failed on port:4444; Nested E
Xception is:
Java.net.SocketException:No buffer space available (maximum connections
Reached?): Listen failed
I Depend on:
Jboss:service=transactionmanager
Depends on Me:
Jboss:service=proxyfactory,target=clientusertransactionfactory
Jboss:service=proxyfactory,target=clientusertransaction
Jboss.jmx:name=invoker,protocol=jrmp,service=proxyfactory,type=adaptor
Jboss.jca:name=defaultds,service=datasourcebinding

At Org.jboss.deployment.MainDeployer.checkIncompleteDeployments (MAINDEPL
oyer.java:1286)
At Org.jboss.deployment.MainDeployer.deploy (maindeployer.java:741)
At Org.jboss.deployment.MainDeployer.deploy (maindeployer.java:722)
At Sun.reflect.NativeMethodAccessorImpl.invoke0 (Native method)
At Sun.reflect.NativeMethodAccessorImpl.invoke (Nativemethodaccessorimpl.
JAVA:39)
At Sun.reflect.DelegatingMethodAccessorImpl.invoke (delegatingmethodacces
SORIMPL.JAVA:25)
At Java.lang.reflect.Method.invoke (method.java:324)
At Org.jboss.mx.interceptor.ReflectedDispatcher.invoke (reflecteddispatch
er.java:141)
At Org.jboss.mx.server.Invocation.dispatch (invocation.java:80)
At Org.jboss.mx.interceptor.AbstractInterceptor.invoke (abstractintercept
or.java:121)
At Org.jboss.mx.server.Invocation.invoke (invocation.java:74)
At Org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke (Modelm
beanoperationinterceptor.java:127)
At Org.jboss.mx.server.Invocation.invoke (invocation.java:74)
At Org.jboss.mx.server.AbstractMBeanInvoker.invoke (Abstractmbeaninvoker.
java:249)
At Org.jboss.mx.server.MBeanServerImpl.invoke (mbeanserverimpl.java:644)
At Org.jboss.mx.util.MBeanProxyExt.invoke (mbeanproxyext.java:177)
At $Proxy 5.deploy (Unknown Source)
At Org.jboss.system.server.ServerImpl.doStart (serverimpl.java:434)
At Org.jboss.system.server.ServerImpl.start (serverimpl.java:315)
At Org.jboss.Main.boot (main.java:195)
At Org.jboss.main$1.run (main.java:463)
At Java.lang.Thread.run (thread.java:534)
14:52:58,270 error [Http11protocol] Error starting Endpoint
Java.net.SocketException:No buffer space available (maximum connections reached
?): Listen failed
At Java.net.PlainSocketImpl.socketListen (Native method)
At Java.net.PlainSocketImpl.listen (plainsocketimpl.java:343)
At Java.net.ServerSocket.bind (serversocket.java:319)
At Java.net.serversocket.<init> (serversocket.java:185)
At Org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket (De
FAULTSERVERSOCKETFACTORY.JAVA:55)
At Org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint (pooltcpendpoi
nt.java:294)
At Org.apache.tomcat.util.net.PoolTcpEndpoint.startEndpoint (POOLTCPENDPO
int.java:312)
At Org.apache.coyote.http11.Http11Protocol.start (http11protocol.java:182
)
At Org.apache.catalina.connector.Connector.start (connector.java:1001)
At Org.jboss.web.tomcat.tc5.Tomcat5.startConnectors (tomcat5.java:492)
At Org.jboss.web.tomcat.tc5.Tomcat5.handleNotification (tomcat5.java:521)

At Sun.reflect.GeneratedMethodAccessor3.invoke (Unknown Source)
At Sun.reflect.DelegatingMethodAccessorImpl.invoke (delegatingmethodacces
SORIMPL.JAVA:25)
At Java.lang.reflect.Method.invoke (method.java:324)
At Org.jboss.mx.notification.NotificationListenerProxy.invoke (Notificati
onlistenerproxy.java:138)
At $Proxy 23.handleNotification (Unknown Source)
At Org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotificat
Ion (jbossnotificationbroadcastersupport.java:112)
At Org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotificatio
N (jbossnotificationbroadcastersupport.java:93)
At Org.jboss.system.server.ServerImpl.sendNotification (serverimpl.java:8
54)
At Org.jboss.system.server.ServerImpl.doStart (serverimpl.java:449)
At Org.jboss.system.server.ServerImpl.start (serverimpl.java:315)
At Org.jboss.Main.boot (main.java:195)
At Org.jboss.main$1.run (main.java:463)
At Java.lang.Thread.run (thread.java:534)
14:52:58,270 WARN [TOMCAT5] Failed to Startconnectors
Lifecycleexception:protocol handler Start Failed:java.net.SocketException:No
Buffer space available (maximum connections reached?): Listen failed
At Org.apache.catalina.connector.Connector.start (connector.java:1003)
At Org.jboss.web.tomcat.tc5.Tomcat5.startConnectors (tomcat5.java:492)
At Org.jboss.web.tomcat.tc5.Tomcat5.handleNotification (tomcat5.java:521)

At Sun.reflect.GeneratedMethodAccessor3.invoke (Unknown Source)
At Sun.reflect.DelegatingMethodAccessorImpl.invoke (delegatingmethodacces
SORIMPL.JAVA:25)
At Java.lang.reflect.Method.invoke (method.java:324)
At Org.jboss.mx.notification.NotificationListenerProxy.invoke (Notificati
onlistenerproxy.java:138)
At $Proxy 23.handleNotification (Unknown Source)
At Org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotificat
Ion (jbossnotificationbroadcastersupport.java:112)
At Org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotificatio
N (jbossnotificationbroadcastersupport.java:93)
At Org.jboss.system.server.ServerImpl.sendNotification (serverimpl.java:8
54)
At Org.jboss.system.server.ServerImpl.doStart (serverimpl.java:449)
At Org.jboss.system.server.ServerImpl.start (serverimpl.java:315)
At Org.jboss.Main.boot (main.java:195)
At Org.jboss.main$1.run (main.java:463)
At Java.lang.Thread.run (thread.java:534)
14:52:58,270 INFO [Server] JBoss (MX microkernel) [4.0.2 (Build:cvstag=jboss_4
_0_2 date=200505022023)] started in 2m:16s:391ms

This is the solution to everyone's ideas:

Your reason is that the socket connection pool is too small, or the connection is not released to be filled, you can first check the number of connections under DOC command Netstat-na if many connections are time_wait, then it is possible that Apache has a lot of discarded connections, You go to Apache inside the httpd.conf modify configuration Keepalive=on. Reboot. Method Two: May be the server automatic Update application occupies the socket resource, therefore disables the service: Background Intelligent Transfer Service. and restart the computer.

Set Apache configuration setsolinger=1, which then forces the connection to be released by default one second

Later, I also studied a bit jboos, we said that the settings really did not find a place, and then restarted the computer, restart the service, the QC can be opened. Summed up, it is estimated that the connection was released, and can be connected, and modified a keepalive original is 6000, now changed to 600, this has yet to be the test of time, then paste the results out.