tomcat 在压力测试下 cpu 一直99% 怎么解决 我主要是在tomcat5里面配置了 我的一个 路径搜索的 webservice供客户端调用。再没有 压力测试的情况 基本 不会 出现这种情况 可是一旦 用进行web压力测试(用微软自带的姚立测试工具)有什么好的解决方法? 解决方案 » 免费领取超大流量手机卡,每月29元包185G流量+100分钟通话, 中国电信官方发货 我的环境是 win2003+tomcat5.0 +jdk1.4.2 出现99%并且一直不恢复有不有可能 是因为 算法出现了死循环引起的吗?但是 我压力测试 的 录制的 两点间计算路径 没有出现死循环阿有不有可能 通过优化 tomcat设置 避免此情况出现? 连接池是不是用tomcat的,没释放? OnlyFor_love(『不给我分 就剪掉楼主小鸡几』) :tomcat可以集群?不是吧! 我仔细看了一下 tomcat5的日志 发现 到后来 好像根本没有执行 我的程序。我是通过 jbuilder2005生成的webservice下面是截取 log部分以下是Log的前面部分:209375 DEBUG 2006-08-18 12:10:07500 [http-8081-Processor16] (RPCProvider.java:228) - value: 8271209375 DEBUG 2006-08-18 12:10:07500 [http-8081-Processor15] (RPCProvider.java:228) - value: 8271209390 DEBUG 2006-08-18 12:10:07515 [http-8081-Processor14] (RPCProvider.java:228) - value: 8271209390 DEBUG 2006-08-18 12:10:07515 [http-8081-Processor13] (RPCProvider.java:228) - value: 8271209390 DEBUG 2006-08-18 12:10:07515 [http-8081-Processor20] (RPCProvider.java:228) - value: 8271209406 DEBUG 2006-08-18 12:10:07531 [http-8081-Processor25] (AbstractConcurrentReadCache.java:1097) - persistStore called (key=4777)209421 INFO 2006-08-18 12:10:07546 [http-8081-Processor25] (netrouter.java:388) - 计算 8345 to 8271路径成功!下面日志后面部分 :好像根本就没有我的程序的日志信息407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor128] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(popHandler00)407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor129] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(empty00)407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor127] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(popHandler00)407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor130] (NSStack.java:103) - NSPop (empty)407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor128] (DeserializationContextImpl.java:802) - Popping handler org.apache.axis.message.RPCHandler@12fe1d2407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor129] (NSStack.java:103) - NSPop (empty)407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor127] (DeserializationContextImpl.java:802) - Popping handler org.apache.axis.message.RPCHandler@92c787407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor130] (DeserializationContextImpl.java:1079) - Popped element stack to org.apache.axis.message.SOAPBody:Body407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor128] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(setProp00)407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor129] (DeserializationContextImpl.java:1079) - Popped element stack to org.apache.axis.message.SOAPBody:Body407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor127] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(setProp00)407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor130] (DeserializationContextImpl.java:1080) - Exit: DeserializationContextImpl::endElement()407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor128] (RPCHandler.java:316) - Setting MessageContext property in RPCHandler.endElement().407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor129] (DeserializationContextImpl.java:1080) - Exit: DeserializationContextImpl::endElement()407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor127] (RPCHandler.java:316) - Setting MessageContext property in RPCHandler.endElement().407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor130] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(value00)407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor128] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(empty00)407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor129] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(value00)407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor127] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(empty00)407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor130] (RPCProvider.java:228) - value: 6872407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor128] (NSStack.java:103) - NSPop (empty)407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor129] (RPCProvider.java:228) - value: 6872407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor127] (NSStack.java:103) - NSPop (empty)407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor130] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(value00)407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor128] (DeserializationContextImpl.java:1079) - Popped element stack to org.apache.axis.message.SOAPBody:Body407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor129] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(value00)407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor127] (DeserializationContextImpl.java:1079) - Popped element stack to org.apache.axis.message.SOAPBody:Body407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor130] (RPCProvider.java:228) - value: 1912 有没有 单独的 profiler工具 的?jbuilder2005集成了个还有没有别的怎么用? 是不是应该用EJB来做?还是换一个像weblogic这样的server? 重要经验:1,你测试时 1~200 压力可能没有任何问题 响应时间,吞吐量,CPU都非常好2,当你的测试达到 一个用户数,比如 200 或者到 1000 TOMCAT的性能会急剧下降,包括WEBSPHERE也是一样的。 按照道理:响应时间由于用户量的增加会变大。 但是吞吐量应当到了一定的压力后保持稳定。 但是我观测的结果是急剧下降。3,解决办法:前面放一个APACHE ,后面多启动几个 TOMCAT端口服务就可以改变这个状况。压力测试怪事多,须谨慎。 据说tomcat 并发数上限100左右? 我数据库连接池 写的有问题(我是要用arcsde 所以没有办法用 tomcat的连接池)导致 死锁 servlet的访问地址问题 ibatis+struts2+spring的过程 怎么办,我没分了?表单自动提交问题? 【询问】在操作Statement,Connection的时候赋值为null和调用close方法有什么区别! 在网页中嵌入的RM插件怎么没有视频 配置过log4j的进来看一下 为什么我怎么配置都说我加载错误 100分:Java与json问题 熟悉java和json的帮看一下 一个很急的问题,请大家帮忙看看!!!必有重谢!!! 关于JSP页面编码的问题 jQuery中的弹出窗口怎么写?相当于html中的alert() 求一个表实现增删改的代码 请问这个问题怎么解决? 在线=啊
有不有可能 是因为 算法出现了死循环引起的吗?
但是 我压力测试 的 录制的 两点间计算路径 没有出现死循环阿有不有可能 通过优化 tomcat设置 避免此情况出现?
我是通过 jbuilder2005生成的webservice下面是截取 log部分
以下是Log的前面部分:
209375 DEBUG 2006-08-18 12:10:07500 [http-8081-Processor16] (RPCProvider.java:228) - value: 8271
209375 DEBUG 2006-08-18 12:10:07500 [http-8081-Processor15] (RPCProvider.java:228) - value: 8271
209390 DEBUG 2006-08-18 12:10:07515 [http-8081-Processor14] (RPCProvider.java:228) - value: 8271
209390 DEBUG 2006-08-18 12:10:07515 [http-8081-Processor13] (RPCProvider.java:228) - value: 8271
209390 DEBUG 2006-08-18 12:10:07515 [http-8081-Processor20] (RPCProvider.java:228) - value: 8271
209406 DEBUG 2006-08-18 12:10:07531 [http-8081-Processor25] (AbstractConcurrentReadCache.java:1097) - persistStore called (key=4777)
209421 INFO 2006-08-18 12:10:07546 [http-8081-Processor25] (netrouter.java:388) - 计算 8345 to 8271路径成功!下面日志后面部分 :好像根本就没有我的程序的日志信息
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor128] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(popHandler00)
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor129] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(empty00)
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor127] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(popHandler00)
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor130] (NSStack.java:103) - NSPop (empty)
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor128] (DeserializationContextImpl.java:802) - Popping handler org.apache.axis.message.RPCHandler@12fe1d2
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor129] (NSStack.java:103) - NSPop (empty)
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor127] (DeserializationContextImpl.java:802) - Popping handler org.apache.axis.message.RPCHandler@92c787
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor130] (DeserializationContextImpl.java:1079) - Popped element stack to org.apache.axis.message.SOAPBody:Body
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor128] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(setProp00)
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor129] (DeserializationContextImpl.java:1079) - Popped element stack to org.apache.axis.message.SOAPBody:Body
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor127] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(setProp00)
407250 DEBUG 2006-08-18 12:13:25375 [http-8081-Processor130] (DeserializationContextImpl.java:1080) - Exit: DeserializationContextImpl::endElement()
407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor128] (RPCHandler.java:316) - Setting MessageContext property in RPCHandler.endElement().
407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor129] (DeserializationContextImpl.java:1080) - Exit: DeserializationContextImpl::endElement()
407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor127] (RPCHandler.java:316) - Setting MessageContext property in RPCHandler.endElement().
407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor130] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(value00)
407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor128] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(empty00)
407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor129] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(value00)
407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor127] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(empty00)
407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor130] (RPCProvider.java:228) - value: 6872
407265 DEBUG 2006-08-18 12:13:25390 [http-8081-Processor128] (NSStack.java:103) - NSPop (empty)
407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor129] (RPCProvider.java:228) - value: 6872
407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor127] (NSStack.java:103) - NSPop (empty)
407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor130] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(value00)
407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor128] (DeserializationContextImpl.java:1079) - Popped element stack to org.apache.axis.message.SOAPBody:Body
407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor129] (ProjectResourceBundle.java:72) - org.apache.axis.i18n.resource::handleGetObject(value00)
407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor127] (DeserializationContextImpl.java:1079) - Popped element stack to org.apache.axis.message.SOAPBody:Body
407281 DEBUG 2006-08-18 12:13:25406 [http-8081-Processor130] (RPCProvider.java:228) - value: 1912
jbuilder2005集成了个
还有没有别的
怎么用?
还是换一个像weblogic这样的server?
1,你测试时 1~200 压力可能没有任何问题
响应时间,吞吐量,CPU都非常好2,当你的测试达到 一个用户数,比如 200 或者到 1000
TOMCAT的性能会急剧下降,包括WEBSPHERE也是一样的。
按照道理:响应时间由于用户量的增加会变大。
但是吞吐量应当到了一定的压力后保持稳定。 但是我观测的结果是急剧下降。3,解决办法:前面放一个APACHE ,后面多启动几个 TOMCAT端口服务就可以改变这个状况。
压力测试怪事多,须谨慎。