The Jboss log file doesn't tell us what's the real reason make the server hanging up totally, just too much information there is actually no information... Is there any monitoring software or tools? Thanks!
JBoss comes with a jmx console. You can make calls to get server runtime statistics. Also thread dumps could also be helpful for troubleshooting server hangs. ( you know, the good old "ctrl-break" or "kill -3"...)
a*y
5 楼
哦? 楼主不是完全原创的?
【在 b**m 的大作中提到】 : : 不错,腰粗了点。 : 给你个参考的:
r*o
6 楼
A bit more complicated, e.g. the server just hang up there ( of course, we can kill -9 always ), we don't know when and why the server hung, not to say to identify which code/application made that happen. I see the jmx statistics and info mbeans, but they are not enough to provide information pin down the error... we are desperate for some real tool here.
【在 m******t 的大作中提到】 : JBoss comes with a jmx console. You can make calls to get server runtime : statistics. : Also thread dumps could also be helpful for troubleshooting server hangs. ( : you know, the good old "ctrl-break" or "kill -3"...)
Thread dumps have always been a good starting point for the client project I 'm working on. We run both Websphere and JBoss. In the case of Websphere, it comes with a set of sophisticated analysis tools. Guess what they try to analyze - thread dumps, and jvm core dumps (if it was _that_ bad). provide here. JConsole? Provided the server isn't really hung as in "hanging dead".
【在 r**o 的大作中提到】 : A bit more complicated, e.g. the server just hang up there ( of course, we : can kill -9 always ), we don't know when and why the server hung, not to : say to identify which code/application made that happen. : I see the jmx statistics and info mbeans, but they are not enough to provide : information pin down the error... we are desperate for some real tool here.