users@glassfish.java.net
Re: How to Trouble-Shoot Infinite Loop in Glassfish
This message
: [
Message body
] [ More options (
top
,
bottom
) ]
Related messages
: [
Next message
] [
Previous message
] [
In reply to
] [
Next in thread
] [
Replies
]
Contemporary messages sorted
: [
by date
] [
by thread
] [
by subject
] [
by author
] [
by messages with attachments
]
From
: <
glassfish_at_javadesktop.org
>
Date
: Fri, 14 Nov 2008 09:08:28 PST
Is there a reason you wouldn't just signal a thread dump and check out the running threads consuming cpu time and see what's on their stack?
You can use sendsignal (
http://www.latenighthacking.com/projects/2003/sendSignal/
)
or VisualVM or Jconsole to get the threaddumps.
You could also utilize something like findbugs / checkstyle / pmd to run an analysis against your code to look for infinite-loop scenarios.
HTH,
Andrew
[Message sent by forum member 'areplogle' (areplogle)]
http://forums.java.net/jive/thread.jspa?messageID=316806
This message
: [
Message body
]
Next message
:
Sahoo: "Re: EJB 3: _at_Remove in Stateless Session Bean"
Previous message
:
glassfish_at_javadesktop.org: "Re: NodeAgent + multi-homed WinXP + JMX Connector URL confusion"
In reply to
:
glassfish_at_javadesktop.org: "How to Trouble-Shoot Infinite Loop in Glassfish"
Next in thread
:
glassfish_at_javadesktop.org: "Re: How to Trouble-Shoot Infinite Loop in Glassfish"
Reply
:
glassfish_at_javadesktop.org: "Re: How to Trouble-Shoot Infinite Loop in Glassfish"
Contemporary messages sorted
: [
by date
] [
by thread
] [
by subject
] [
by author
] [
by messages with attachments
]