On 6/7/2011 12:38 PM, George Niculae wrote: > On Tue, Jun 7, 2011 at 8:27 PM, George Niculae<[email protected]> wrote: >> On Tue, Jun 7, 2011 at 8:11 PM, Matthew Kitchin (public/usenet) >> <[email protected]> wrote: >>> My sipx server at our corporate office (170+ users) has 1 CPU pegged. It >>> is a java process doing this. I haven't received any complaints yet, but >>> I expect them to start before too long. I will reboot it tonight. >>> As far as today, would you expect it to drop active calls if I kill the >>> offending process? Below is everything I know how to show about what the >>> process is doing. >>> 4.2.1, sipxbridge, Polycom 450 and 550 phones >> Try first to restart sipXivr and see if it comes back (Voicemail and AA >> service) >> > 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. 3788), > then open 2 sessions, Since it is fixed, there is nothing more I can do that would be helpful for you guys, right? > in the first session: > cat /proc/3788/fd/1 > > in the 2nd session issue > kill -3 3788 > 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 > > George > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
