QC无法启动，实战记录

今天上午QC还用得好好的，下午就突然打不开了，急了，服务重启了一遍还是不行。最后将错误信息截下来，仔细研究，同时也要感谢测试群的朋友们的帮忙，终于找到了一些方向。

下面把错误信息贴出来：

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: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=-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 $Proxy5.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 $Proxy23.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 $Proxy23.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

这个是大家的解决思路：

你这个原因是socket连接池配制数目太少，或者连接未释放而被占满了,可以先在doc下面查看连接数命令netstat -na 如果很多连接都是TIME_WAIT的，那么可能是apache产生了很多废弃连接，你到apache里面的httpd.conf 修改配置 keepAlive=on.重启。。方法二：可能是服务器自动更新应用占用socket 资源，所以禁用服务:Background Intelligent Transfer Service..然后重启机算机

设置apache配置setSoLinger=1，之后它会默认一秒后强制释放连接

后来，我也研究了一下JBOOS ，大家说的设置真的没找到地方，后来重启了电脑，重启服务，QC就可以打开了。总结了一下，估计是连接释放了，又可以连接上了，同时修改了一个keepAlive原来是6000，现在改成了600，这个还有待时间的考验，到时再贴结果出来吧。

QC无法启动，实战记录相关推荐

【网络通信 -- WebRTC】项目实战记录 -- Chrome 启动参数总结
[网络通信 -- WebRTC]项目实战记录 -- Chrome 启动参数总结 1 -- 报告伪分配跟踪.伪跟踪从当前活动的跟踪事件派生. 2 --/prefetch:1 /prefetch:启动各种 ...
js cookie 存储checkbox_[cookie实战记录-1]种下一个cookie
[cookie实战记录-1]种下一个cookie 引子 cookie ~ 也是前端实际工作中一定会碰到的(哎?为什么要说也呢...) 而且由于前一阵 Chrome 的更新改了关于 cookie sam ...
【网络通信 -- SIP 电话】项目实战记录 -- SIP 服务器 OPENSIPS 搭建测试与 SIP 客户端 PJSIP 编译安装测试
[网络通信 -- SIP 电话]项目实战记录 -- SIP 服务器 OPENSIPS 搭建测试与 SIP 客户端 PJSIP 编译安装测试 [1]SIP 服务器 OPENSIPS 搭建 1.1 安装环 ...
PCL 实战记录（一）
PCL 实战记录 (一) 目录 PCL 实战记录 (一) 1.读取.显示.保存 2.KD-TREE 搜索 3.八叉树点云采样 4.OCTREE 空间分割 5.滤波 6.采样 6.1 下采样 6.2 ...
微信Hook实战记录2:动手实现恶意dll内存插入器
Hook任何软件,整体思路都是通过内存调试软件对软件运行时内存进行断点调试,找到想要hook的内存地址,转为可以通过程序主dll可以获得的相对地址,然后再此处插入自己的恶意汇编代码,如果代码比较复杂, ...
谁动了我的奶酪（数据库）_攻击防范实战记录
谁动了我的奶酪(数据库)_攻击防范实战记录本系列文章由ex_net(张建波)编写,转载请注明出处. http://blog.csdn.net/ex_net/article/details/76479 ...
【网络通信 -- 直播】SRS 实战记录 -- SRS 部署与直播效果测试
[网络通信 -- 直播]SRS 实战记录 -- SRS 部署与直播效果测试 [1]SRS(Simple Realtime Server) 部署 SRS 代码下载 git clone https://g ...
定制SPS实战记录系列之一
定制SPS实战记录系列之一<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" ...
python ui自动化配置文件,python UI自动化实战记录八：添加配置
添加配置文件写入测试地址等,当环境切换时只需修改配置文件即可. 1 在项目目录下添加文件 config.ini 写入: [Domain] domain = http://test.domain.cn ...
SpringBoot 2.0 系列005 --启动实战之SpringApplication应用
为什么80%的码农都做不了架构师?>>> SpringBoot 2.0 系列005 --启动实战之SpringApplication应用 2.X 官方示例注意是只使用了@En ...

QC无法启动，实战记录

QC无法启动，实战记录相关推荐

最新文章

热门文章