Bug 958849
Summary: | Module Service Dependencies do not take transitive dependencies into account | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Herambh <hnaram> | ||||
Component: | Class Loading | Assignee: | Enrique Gonzalez Martinez <egonzale> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.0.1 | CC: | cdewolf, egonzale | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-04-21 08:53:10 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: |
|
I have verified the issue in 6.0.1. This cannot be reproduced in 6.4.x branch (no regression). Looking at the target release, This was fixed in 6.1.0. closing this as a duplicate. *** This bug has been marked as a duplicate of bug 963298 *** |
Created attachment 742721 [details] TestCase Description of problem: 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. Version-Release number of selected component (if applicable): How reproducible: if We put the dependency of rar in ear's jboss-deployment-structure.xml with export=true like below , we see the "Caused by: org.jboss.modules.ModuleNotFoundException: deployment.wmq.jmsra.rar:main" ------------------------------------------------------------------- <jboss-deployment-structure> <deployment> <dependencies> <module name="deployment.wmq.jmsra.rar" export="true"/> </dependencies> </deployment> </jboss-deployment-structure> ------------------------------------------------------------------- However, if We put the dependency of jar in ear's jboss-deployment-structure.xml with export=true like below , there is no error seen. ------------------------------------------------------------------- <jboss-deployment-structure> <deployment> <dependencies> <module name="deployment.TestEJB2.jar" export="true" /> </dependencies> </deployment> </jboss-deployment-structure> ------------------------------------------------------------------- To overcome the scenario , we change the content of ear's META-INF/jboss-deployment-structure.xml like below and it works. -------------------------------------------------------------------------------- <jboss-deployment-structure> <deployment> <dependencies> <module name="deployment.wmq.jmsra.rar" export="true" /> </dependencies> </deployment> <!-- NOTICE FOLLOWING --> <sub-deployment name="messageservice.jar"> <dependencies> <module name="deployment.wmq.jmsra.rar" export="true" /> </dependencies> </sub-deployment> </jboss-deployment-structure> -------------------------------------------------------------------------------- Steps to Reproduce: Refer attached TestCase.zip. It contains the rar and a EJB jar. Implement the above steps to reproduce the issue. Actual results: Expected results: Additional info: