Bugs item #693326, was opened at 2003-02-26 12:04
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=693326&group_id=22866
Category: JBossMX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Brian Wallis (bwallis42)
Assigned to: Nobody/Anonymous (nobody)
Summary: Deadlock between threads "main"/"JBoss Shutdown Hook"
Initial Comment:
OS: Mandrake Linux 8.0 with Redhat 7.2 kernel (2.4.7-10)
arch: i386
jdk: SUN JDK 1.4.1_01
JBoss Version: 3.0.4
While starting jboss for a test I realised I had forgotten
something and hit control-C to shut it down again. The
startup had got to starting deployment of
jbossmq-service.xml when the shutdown began.
It got as far as starting to undeploy jbossmq.jar and
deadlocked
The jboss server trace is attached in a file including a
deadlock report from the JVM showing what is locked and
why it is deadlocked.
Reproducing this may be difficult, it is no doubt very timing
sensitive to when the shutdown starts. There should be
enough info in the thread stack traces to find the problem.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=693326&group_id=22866
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
