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/

Reply via email to