Bug 958849 - Module Service Dependencies do not take transitive dependencies into account
Summary: Module Service Dependencies do not take transitive dependencies into account
Keywords:
Status: CLOSED DUPLICATE of bug 963298
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Class Loading
Version: 6.0.1
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Enrique Gonzalez Martinez
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-02 14:19 UTC by Herambh
Modified: 2018-12-02 17:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-21 08:53:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
TestCase (6.57 MB, application/zip)
2013-05-02 14:19 UTC, Herambh
no flags Details

Description Herambh 2013-05-02 14:19:08 UTC
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:

Comment 2 Enrique Gonzalez Martinez 2015-04-21 08:53:10 UTC
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 ***


Note You need to log in before you can comment on or make changes to this bug.