On Wed, Aug 10, 2011 at 4:40 PM, Subbotkin, Nikolay <[email protected]> wrote:
> Sorry i not seen this email. I now see now.
> No, backup no used every day, sometimes. This built backup is help ?
>
If and you can do this, in order to figure out why that problem,
identify the pid for the java process eating CPU cycles (e.g. 7128),
then open 2 sessions,
in the first session:
cat /proc/7128/fd/1
in the 2nd session issue
kill -3 7128
then you will see the thread dump in the first console, e.g.:
[root@centosbox ~]# cat /proc/3788/fd/1
2011-03-10 10:25:56
Full thread dump OpenJDK Client VM (14.0-b16 mixed mode):
"P2-19" prio=10 tid=0x09480400 nid=0x14ea in Object.wait() [0x6dac1000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x76e16df8> (a org.mortbay.util.ThreadPool$PoolThread)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:522)
- locked <0x76e16df8> (a org.mortbay.util.ThreadPool$PoolThread)
"P2-18" prio=10 tid=0x0947ec00 nid=0x14e9 in Object.wait() [0x6db12000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x76e16e80> (a org.mortbay.util.ThreadPool$PoolThread)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:522)
- locked <0x76e16e80> (a org.mortbay.util.ThreadPool$PoolThread)
Provide the thread dump from the first session and we'll see what's wrong
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
