Bug 778743 (SOA-1200) - Java-level deadlock when running eap testsuite
Summary: Java-level deadlock when running eap testsuite
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-1200
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: EAP
Version: 4.3 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Rajesh Rajasekaran
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks: SOA-936
TreeView+ depends on / blocked
 
Reported: 2009-03-01 21:04 UTC by Aleksandar Kostadinov
Modified: 2009-03-04 20:43 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
x86_64 multiprocessor
Last Closed: 2009-03-04 20:43:31 UTC
Type: Bug

Attachments (Terms of Use)
soa-eap.tgz (42.65 KB, application/x-gtar)
2009-03-01 21:22 UTC, Aleksandar Kostadinov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1200 0 None None None Never

Description Aleksandar Kostadinov 2009-03-01 21:04:39 UTC 
project_key: SOA

When I run eap test suite against soa-4.3.0.GA_CP01_CR2 binaries I get most tests timing out. To make the long story short I did "kill -3 <jboss  pid>" and saw this deadlock. Reproducible most of the times but might be machine specific.

Found one Java-level deadlock:
=============================
"pool-12-thread-1":
  waiting to lock monitor 0x00000000597ddd20 (object 0x00002aaabf6f3410, a org.j
boss.aop.deployment.JBossClassPool),
  which is held by "RMI TCP Connection(9)-10.16.93.213"
"RMI TCP Connection(9)-10.16.93.213":
  waiting to lock monitor 0x00002aaaf07903f8 (object 0x00002aaab9d859a8, a org.j
boss.mx.loading.UnifiedClassLoader3),
  which is held by "pool-12-thread-1"
Comment 2 Aleksandar Kostadinov 2009-03-01 21:22:27 UTC 
Attachment: Added: soa-eap.tgz
Comment 3 Aleksandar Kostadinov 2009-03-01 21:27:41 UTC 
Rajesh, could you look at the logs and see if you have seen such an issue before? The thread dump with the deadlock explanation is in output.log at the end (case-insensitive search for "deadlock").
I'll run the tests on other similar machines and will report result when I have it.
Comment 5 Aleksandar Kostadinov 2009-03-02 14:53:59 UTC 
Adding this one as a dependency of SOA-936
Comment 6 Aleksandar Kostadinov 2009-03-02 14:53:59 UTC 
Link: Added: This issue is a dependency of SOA-936
Comment 7 Aleksandar Kostadinov 2009-03-04 20:43:31 UTC 
Seems like after updating RHEL5 to current, tests don't crash any more. Closing as Rejected.
Note You need to log in before you can comment on or make changes to this bug.