-
1. Re: Updating deployment with dependant
gamba Aug 20, 2013 6:57 AM (in response to ansur)We have the same problem with EA 6.0.1. Is this redeployment issue fixed with 6.1.0?
-
2. Re: Updating deployment with dependant
ctomc Aug 20, 2013 7:06 AM (in response to gamba)Gamba wrote:
We have the same problem with EA 6.0.1. Is this redeployment issue fixed with 6.1.0?
It should be.
-
3. Re: Updating deployment with dependant
gamba Aug 27, 2013 8:41 AM (in response to ansur)I tried with EAP 6.1.0. After a redeployment the app1 to a running server my dependant EAR app2 throws still an error:
14:33:15,218 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."app2.ear".PARSE: org.jboss.msc.service.StartEx
ception in service jboss.deployment.unit."app2.ear".PARSE: JBAS018733: Failed to process phase PARSE of deployment "app2.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_20]
at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_20]
Caused by: java.lang.IllegalStateException
at org.jboss.as.webservices.util.ASHelper.getRequiredAttachment(ASHelper.java:162)
at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_EJB.processAnnotation(WSIntegrationProcessorJAXWS_EJB.java:81)
at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_EJB.deploy(WSIntegrationProcessorJAXWS_EJB.java:70)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
... 5 more
A reload or restart of the server solves this problem and the applications are now start in correct order (in former version 6.0.1 applications are not started
in correct order after an redeployment).
I guessed that this fixes the fromerly known redeployment error: https://issues.jboss.org/browse/AS7-5410
In all ears I have a jboss-all.xml in META-INF-directory:
<jboss umlns="urn:jboss:1.0">
<jboss-deployment-dependencies xmlns="urn:jboss:deployment-dependencies:1.0">
<dependency name="app1.ear" />
</jboss-deployment-dependencies>
</jboss>
-
4. Re: Updating deployment with dependant
ansur Sep 3, 2013 2:40 AM (in response to ansur)FYI I created an issue for this problem a while ago: [#WFLY-1363] Updating deployment with dependant - JBoss Issue Tracker
-
5. Re: Updating deployment with dependant
gamba Sep 3, 2013 3:39 AM (in response to ansur)Thank you for the link. I vote for it.
Currently our nightly-build is broken, because of this issue.
Reload with jboss-as-maven-plugin seems not to work after redeployment so I have
to figure out a workaround ... with Ant or some some other plugin.