You have to cat proc/fd pid while kill -3 to get something, check wiki George
On Saturday, September 15, 2012, Matt White <[email protected]> wrote: > kill -3 <pid> does not work. I'm not sure if its because the process is stuck but I can use on other java process but not the one stuck at 100% > > Thats why i tried jack as its already available on the machine. > > -m > >>>> Alex Mateescu <[email protected]> 09/15/12 10:16 AM >>> > kill -3 <pid>, optionally redirected to a file seems to work better than jstack, though it will show the running threads, not how much CPU they use. For that, you'd need to connect a profiler (e.g. VisualVM) to the running process. > > Alex > > On Fri, Sep 14, 2012 at 10:32 PM, George Niculae <[email protected]> wrote: > > Try using > > jmap -F -dump:file=dump.map PID > > Loading in MemoryAnalyzerTool reveals issues > > George > > On Friday, September 14, 2012, Matt White <[email protected]> wrote: >> Yup. >> >> But looking at the stack I dont think it really shows much. I see alot of these: Error occurred during stack walking: >> >> A quick google would show jstack cant always walk the stack when its hung, so I'm not sure its valid. >> >> Its easy to replicate, copy over the jain-sip-sdp and restart call control. Utilization goes to 100%. >> Copy the old one back and restart call control and it goes back to normal. >> >> When I have some spare time I might go back through some older releases of jain-sip and see if the issue started at a specific release. >> >> -M >> >>>>> Douglas Hubler <[email protected]> 09/14/12 2:57 PM >>> >> this is when is was consuming 100% of CPU? >> >> On Fri, Sep 14, 2012 at 2:42 PM, Matt White <[email protected]> wrote: >>> I used jstack to get a dump of the thread. >>> >>> Contents available on pastebin: http://pastebin.com/qDSFC4HE >>> >>>>>> Douglas Hubler <[email protected]> 09/13/12 8:18 PM >>> >>> >>> On Thu, Sep 13, 2012 at 7:56 PM, Matt White <[email protected]> >>> wrote: >>>> Just thought I'd give an update on updating the jain-sip >>>> >>>> I've put this latest jain-sip in production on 3 system for several weeks >>>> now. One 4.2.1 and the other 2 are 4.4 >>>> >>>> They are working fine and there is no useability issues. However the >>>> sipxrest java process pegs at 100%. >>>> >>>> Our systems are multi-core so it doesnt affect system usage. >>>> >>>> Setting the call control logs to debug dont show any additional detail. >>>> >>>> Is there a good way to debug the sipxrest process. >>> >>> there was some way to dump the java thread and by calling kill -3 on >>> the process and then cat'ing a file descriptor, but i cannot recall >>> the exact sequence. Anyone recall? >>> _______________________________________________ >>> 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/ >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive:
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
