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.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 $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，这个还有待时间的考验，到时再贴结果出来吧。

本文来自互联网用户投稿，该文观点仅代表作者本人，不代表本站立场。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如若转载，请注明出处：http://www.mzph.cn/news/415754.shtml

如若内容造成侵权/违法违规/事实不符，请联系多彩编程网进行投诉反馈email:809451989@qq.com，一经查实，立即删除！

相关文章

android butterknife使用详解

android butterknife使用详解

添加依赖 compile com.jakewharton:butterknife:8.6.0 annotationProcessor com.jakewharton:butterknife-compiler:8.6.0 //下载最新黄油刀 implementation com.jakewharton:butterknife:10.2.0 annotationProcessor com.jakewharton:butterknife-compiler:10.2.0 …
阅读更多...
工作108:swiper使用

工作108:swiper使用

<!--首页管理--> <template><div><el-card><h1>等待处理</h1><div style"width: 100%;height: 200px"><swiper ref"mySwiper" ><swiper-slide v-for"(item,index) in task"><el-butt…
阅读更多...
背景图片生成网站收集

背景图片生成网站收集

https://pissang.github.io/little-big-city/ 生成星球 https://alteredqualia.com/ 很多效果 http://www.decrooks.com/ 毛线球生成器
阅读更多...
python入门-分类和回归各种初级算法

python入门-分类和回归各种初级算法

引自&#xff1a;http://www.cnblogs.com/taichu/p/5251332.html ########################### #说明&#xff1a; # 撰写本文的原因是&#xff0c;笔者在研究博文“http://python.jobbole.com/83563/”中发现 # 原内容有少量笔误&#xff0c;并且对入门学友缺少一些…
阅读更多...
工作109:控制mode跳转

工作109:控制mode跳转

阅读更多...
Git Bash下载安装，git命令下载项目，上传android项目到github步骤，以及取消项目关联Git，设置git忽略文件

Git Bash下载安装，git命令下载项目，上传android项目到github步骤，以及取消项目关联Git，设置git忽略文件

设置忽略文件 1、工程下创建文件夹gitignore。push即可 *.iml .gradle /local.properties /.idea/caches /.idea/libraries /.idea/modules.xml /.idea/workspace.xml /.idea/navEditor.xml /.idea/assetWizardSettings.xml .DS_Store /build /captures .externalNativeBuild …
阅读更多...
软件测试是找BUG，不是找茬

软件测试是找BUG，不是找茬

做测试久了&#xff0c;经常会有一些感悟&#xff0c;最近在51上看到一贴&#xff0c;说出了我的心声&#xff0c;把我一直想写却一直以时间为借口为由拖着未写的心声写出来&#xff0c;摘抄了部分过不&#xff0c;一起纪念测试的年代&#xff0c;测试的心声。测试好象一直会被…
阅读更多...
比较精确的js倒计时实现

比较精确的js倒计时实现

// 传入需要倒计时的秒数countDown(times) {// 时间间隔 1秒const interval 1000;// 计算时间&#xff0c;转化为毫秒let ms times * 1000;let count 0;const startTime new Date().getTime();const endTime startTime ms;let timeCounter;timeCounter setTimeout(count…
阅读更多...
java 如何让循环结束，跳过某个条件，跳出当前的多重嵌套循环

java 如何让循环结束，跳过某个条件，跳出当前的多重嵌套循环

当数据比较庞大的时候&#xff0c;需要循环遍历某个数据的时候可用 for (int ab 0;ab<10000;ab){if (ab 7){//当找到7的时候&#xff0c;结束循环Log.v("map","..ab 7....11......"ab);break;}else {Log.v("map","......11..else....&qu…
阅读更多...
工作110:表格重置

工作110:表格重置

阅读更多...
服务器虚拟化之－——VMware组件与功能。

服务器虚拟化之－——VMware组件与功能。

最近公司提出帮服务器虚拟化&#xff0c;以前也没接触过&#xff0c;在网上搜了一通&#xff0c;查看了一少资料&#xff0c;感觉现在对虚拟化有了一些了解&#xff0c;在售前我们要出方案&#xff0c;需要对虚拟化进行一个整体评估&#xff0c;这步先省略&#xff0c;后期再补…
阅读更多...
vue 获取验证码倒计时组件

vue 获取验证码倒计时组件

之前写过一个计时函数&#xff0c;有计算误差&#xff0c;但是验证码的60秒倒计时可以忽略这一点点误差。直接上代码。 <template><div class"captcha-row"><input class"captcha-input" placeholder"输入验证码" auto-focus …
阅读更多...
【iCore1S 双核心板_FPGA】例程十六：基于SPI的ARM与FPGA通信实验

【iCore1S 双核心板_FPGA】例程十六：基于SPI的ARM与FPGA通信实验

实验现象&#xff1a; 核心代码&#xff1a; int main(void) {int i,n;char buffer[20];char spi_buffer[20];HAL_Init();system_clock.initialize();led.initialize();usart1.initialize(115200);spi.initialize();usart1.printf("Hello! I am iCore1S!\r\n"); …
阅读更多...
WebView纯浏览模式，webView不可点击

WebView纯浏览模式，webView不可点击

方法1&#xff1a; webView.setWebViewClient(new WebViewClient() {Overridepublic boolean shouldOverrideUrlLoading(WebView view, String url) { // view.loadUrl(url);return true;//true时&#xff0c;不可点击跳页效果&#xff0c;false时&#xff0c;可…
阅读更多...
工作111:直接写url

工作111:直接写url

阅读更多...
js 短信验证码 6位数字

js 短信验证码 6位数字

其死后就一样代码&#xff0c;比较简单&#xff0c;但是非常常用 const code (000000 Math.floor(Math.random() * 999999)).slice(-6);
阅读更多...
服务器的性能监测及工具（profmon）

服务器的性能监测及工具（profmon）

在使用PerfMon进行服务器基准测试之前&#xff0c;我们将介绍几个技巧来检测服务器的内存使用情况&#xff0c;以确保内存分配不会影响服务器性能。 Memory:Available Bytes-这个功能检测操作系统(OS)的物理内存总量&#xff0c;并计算服务器上运行所有必须进程和应用程序所需的…
阅读更多...
Android中1像素Activity进程保活

Android中1像素Activity进程保活

背景Android8.0马上就要发布&#xff0c;Google对于安卓市场上各种应用占据内存空间的问题不断进行内存完善&#xff0c;我们的应用进程很难再保持不死之身&#xff0c;以前的服务唤醒在5.0已经失效&#xff0c;现在我们尽可能的做到保活方式就是提高进程的优先级&#xff0c;本…
阅读更多...
工作112:空字符串引发的问题

工作112:空字符串引发的问题

阅读更多...
记录一个奇葩问题 宝塔 nginx: [warn] conflicting server

记录一个奇葩问题 宝塔 nginx: [warn] conflicting server

宝塔面板里面运行很久的nginx&#xff0c;好久没有重启&#xff0c;这次一重启&#xff0c;报错了。 解决方法&#xff0c;去/www/server/panel/vhost/nginx目录下&#xff0c;把相关的历史记录给删掉&#xff0c;再重启&#xff0c;就没有问题了
阅读更多...
最新文章

Copyright @ 2022~2023