Bug 1011634

Summary: ClassLoading deadlock on startup
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: kconner
Component: RT GovernanceAssignee: kconner
Status: CLOSED NOTABUG QA Contact: Jiri Sedlacek <jsedlace>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: atangrin, gbrown, ldimaggi, oskutka, soa-p-jira
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-18 15:13:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Stack dumps of the VM including the identified deadlock at the end none

Description kconner 2013-09-24 16:36:14 UTC 
Created attachment 802350 [details]
Stack dumps of the VM including the identified deadlock at the end

Description of problem:

A deadlock was seen while running up a server on OpenShift, using the RTGov for ER3.  The deadlock occurs deep in the ClassLoading, while 

The version of the JVM is

java version "1.7.0_25"
OpenJDK Runtime Environment (rhel-2.4.1.1.el6-i386)
OpenJDK Server VM (build 24.0-b50, mixed mode)

It looks like it is a bug in the JDK however I believe that weld may have a workaround, https://issues.jboss.org/browse/WELD-1169
Comment 2 kconner 2013-09-24 16:43:42 UTC 
The server reports itself as JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) and is an installation of the current SY + RTGov codebases.
Comment 3 Anne-Louise Tangring 2013-11-11 18:47:19 UTC 
This should be fixed by picking up EAP 6.1.1.
Comment 4 kconner 2013-11-13 16:36:38 UTC 
I double checked the EAP 6.1.1 release and, unfortunately, it does not contain the workaround for this JDK bug.  The fix had been made in the Weld 2.x release stream whereas the EAP 6.1.1 release contains Weld-1.1.13.

There is a separate issue for having this addressed in the 1.x stream, https://issues.jboss.org/browse/WELD-1296.

I believe that this issue has only been seen once to date so it would appear that the window of opportunity is very small.
Comment 5 Gary Brown 2014-06-18 15:13:42 UTC 
Looks like the problem has now been fixed in the jdk: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7122142
Comment 6 kconner 2014-06-26 18:48:14 UTC 
No longer a bug as it has been fixed in the latest JDK