Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 963298

Summary:	Module Service Dependencies do not take transitive dependencies into account
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	jbossas	Assignee:	Brad Maxwell <bmaxwell>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	bmaxwell, cdewolf, hnaram, jcechace, lcosti, rdickens
Target Milestone:	ER3
Target Release:	EAP 6.1.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	There existed an issue in JBoss EAP 6 where dependency graph resolution was not taking into account situations where the `Class-Path` specified in deployment manifests may be transitive. This would result in a module attempting to start before all its dependencies were started, and would cause the application to fail to deploy, resulting in the following exception: ---- Caused by: org.jboss.modules.ModuleLoadException: JBAS018760: Timeout waiting for module service: deployment.example.ear.example-ejb.jar:main ... ---- To fix this issue, a multi-stage resolution process was added to make sure that all dependent module specification services have started before starting a module service. As a result, a deployment should no longer fail where transitive dependencies are specified in its `Class-Path`.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-16 20:29: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:

Description Brad Maxwell 2013-05-15 15:29:29 UTC

Module Service Dependencies do not take transitive dependencies into account 
https://issues.jboss.org/browse/WFLY-920

A ModuleLoadService has dependencies on all its dependent ModuleSpecServices, however this does not work if the ModuleSpecService has a dependency on another ModuleSpecService with export=true, as the module may attempt to load before transitive dependencies have been started.

This has caused transient failures in EarClassPathTransitiveClosureTestCase and causes "JBAS018760: Timeout waiting for module service" for a user with jars in ear/lib and many jars using Class-Path 

Caused by: org.jboss.modules.ModuleLoadException: JBAS018760: Timeout waiting for module service: deployment.test.ear.lib/generated/test.jar:main
  at org.jboss.as.server.moduleservice.ServiceModuleLoader$ModuleSpecLoadListener.getModuleSpec(ServiceModuleLoader.java:133) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
  at org.jboss.as.server.moduleservice.ServiceModuleLoader.findModule(ServiceModuleLoader.java:174) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

Comment 3 Brad Maxwell 2013-05-24 15:48:45 UTC

Flags have been updated, so we have 6.1.1 now, so changing proposal from 6.2 to 6.1.1 since this is a bug.

Comment 4 Jakub Cechacek 2013-08-07 08:29:59 UTC

Verified 6.1.1.ER4

EarClassPathTransitiveClosureTestCase passed

Comment 9 Enrique Gonzalez Martinez 2015-04-21 08:53:10 UTC

*** Bug 958849 has been marked as a duplicate of this bug. ***