[jboss-jira] [JBoss JIRA] (WFLY-1363) Updating deployment with dependant

[Brad Maxwell (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129740#comment-13129740 ] 

Brad Maxwell commented on WFLY-1363:
------------------------------------

Looks like duplicate of https://issues.jboss.org/browse/WFLY-975 - which is fixed in wildfly, I tested wildfly-10.0.0.CR4 , deployed a depends on b, then redeployed a and then redeployed b, and did not get the IllegalStateException that I saw in EAP 6.4, so I would say this Wildfly jira is resolved in Wildlfy



> Updating deployment with dependant
> ----------------------------------
>
>                 Key: WFLY-1363
>                 URL: https://issues.jboss.org/browse/WFLY-1363
>             Project: WildFly
>          Issue Type: Bug
>          Components: Server
>         Environment: Windows 7 64bit, JBoss 7.2.0.Final
>            Reporter: Bart Van Dosselaer
>            Assignee: Jason Greene
>              Labels: deployment
>         Attachments: jboss-deployment.zip, jboss-deployment.zip
>
>
> I'm faced with a certain deployment issue, for which I've created a small maven project (see attachment) so anyone can easily reproduce this behaviour.
>  
> I have a scenario where I have two EAR deployments: base.ear and service.ear. The latter uses some services of the former. For this to work, it has all the necessary entries in its manifest.
> Once deployed, I can call the EJB from service.ear and the EJB from base.ear gets injected and used. No problems so far.
>  
> This works fine, until I want to update base.ear.
>  
> We have our own mechanism to update deployments (through the management API), but the same result can be achieved by deploying through the JBoss Admin console or JBoss CLI.
> So, when I update base.ear (just replace with the same base.ear file) it deploys fine and the invocation is successful. However, there's one line in the console which goes like:
> JBAS014777:   Services which failed to start:      service jboss.deployment.subunit."service.ear"."service-ejb.jar".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."service.ear"."service-ejb.jar".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of subdepl
> oyment "service-ejb.jar" of deployment "service.ear"
> At this moment, the service.ear, and all its EJBs, isn't really deployed anymore. Or atleast, wrongfully deployed. Not sure how to call that state.
> One possibility is to invoke the :reload command (or restart the server), but ideally we'd like to not have this error in the first place.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)