[CDAGEN-636] Cannot deploy CDAGenerator 2.1.1 in

[CDAGEN-636] Cannot deploy CDAGenerator 2.1.1 in ovh2 Created: 13/Jan/17 Updated:
16/Jan/17 Resolved: 16/Jan/17
Status:
Closed
Project:
CDA Gazelle Objects Checker
Component/s:
None
Affects
Version/s:
2.1.0
Fix Version/s:
2.1.2
Type:
Bug
Priority:
Blocker
Reporter:
Anne-Gaelle Berge
Assignee:
Anne-Gaelle Berge
Resolution:
Fixed
Votes:
0
Labels:
None
Remaining
Estimate:
0 minutes
Time Spent:
2 hours
Original
Estimate:
1 hour
Issue Links:
Relates
relates to
HLVAL-327
When updating to gazelle-tools:3.0.25...
Closed
relates to
DDS-160
When updating to gazelle-tools:3.0.25...
Closed
relates to
OM-309
When updating to gazelle-tools:3.0.25...
Closed
relates to
PAM-408
When updating to gazelle-tools:3.0.25...
Closed
relates to
PROXY-163
When updating to gazelle-tools:3.0.25...
Closed
relates to
SCHVAL-123
When updating to gazelle-tools:3.0.25...
Closed
relates to
SVS-172
When updating to gazelle-tools:3.0.25...
Closed
relates to
GSS-404
When updating to gazelle-tools:3.0.25...
Submitted
relates to
HPD-64
When updating to gazelle-tools:3.0.25...
Submitted
relates to
XDSTAR-510
When updating to gazelle-tools:3.0.25...
Submitted
relates to
XDW-118
When updating to gazelle-tools:3.0.25...
Submitted
Sprint:
2017 - S1
Account:
Maintenance 2016 (MAINTENANCE2016)
Description
Deploying CDAGenerator 2.1.1 in ovh2 (with Gazelle X Validator Rule Editor) throws the following exception (and crashes
jboss)
[0m[0m11:34:29,526 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2)

Creating Service {http://ws.mb.validator.gazelle.ihe.net}ModelBasedValidationWSService from class
net.ihe.gazelle.cda.validator.ws.CDAValidatorWS
[0m[31m11:34:29,565 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service
jboss.deployment.subunit."CDAGenerator.ear"."CDAGenerator-ejb.jar".INSTALL: org.jboss.msc.service.StartException in
service jboss.deployment.subunit."CDAGenerator.ear"."CDAGenerator-ejb.jar".INSTALL: JBAS018733: Failed to process
phase INSTALL of subdeployment "CDAGenerator-ejb.jar" of deployment "CDAGenerator.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-
server-7.2.0.Final.jar:7.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-
1.0.4.GA.jar:1.0.4.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-
1.0.4.GA.jar:1.0.4.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_80]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_80]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_80]
Caused by: javax.xml.ws.WebServiceException: java.lang.reflect.UndeclaredThrowableException
at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:368)
at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:67)
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:250)
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:536)
at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:116)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:128)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:67)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:74)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-
server-7.2.0.Final.jar:7.2.0.Final]
... 5 more
Caused by: java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy49.visitLabel(Unknown Source)
at org.apache.cxf.jaxws.WrapperClassGenerator.createWrapperClass(WrapperClassGenerator.java:223)
at org.apache.cxf.jaxws.WrapperClassGenerator.generate(WrapperClassGenerator.java:137)
at
org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.generatedWrapperBeanClass(JaxWsServiceFactoryBean.java:669)
at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.getExtraClass(JaxWsServiceFactoryBean.java:638)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:472)
at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:690)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:540)
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:252)
at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:205)
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:101)
at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:159)
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211)
at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:453)

at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:333)
... 13 more
Caused by: java.lang.NoSuchMethodException: org.objectweb.asm.MethodWriter.visitLabel(org.objectweb.asm.Label)
at java.lang.Class.getMethod(Class.java:1678) [rt.jar:1.7.0_80]
at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:52)
... 28 more
Comments
Comment by Anne-Gaelle Berge [ 13/Jan/17 ]
Voila le constat que je fais suite à plusieurs tests:
CDAGenerator (avec gazelle-tools:3.0.25 sans le fix) + GazelleXValidatorRuleEditor (vieille
version de gazelle-tools) ==> KO
CDA Generator (avec gazelle-tools:3.0.25 sans le fix) + GazelleXValidatorRuleEditor (gazelle-
tools:3.0.25 + fix) ==> KO
CDA Generator (avec gazelle-tools:3.0.25 + fix ) + GazelleXValidatorRuleEditor (vieille
version de gazelle-tools) ==> OK
CDA Generator (avec gazelle-tools:3.0.25 + fix) + GazelleXValidatorRuleEditor (gazelle-
tools:3.0.25 + fix) ==> OK
Si vous avez mis à jour votre projet en utilisant gazelle-tools:3.0.25. Il vous faut vérifier que
vous avez fait les changements suivants au risque de ne pas pouvoir déployer votre ear. Il
semblerait que le problème soit rencontré quand l'application expose des web services SOAP.
Ce qui est rassurant avec mes tests, c'est qu'il ne semble pas nécessaire de rebuilder toutes les
applications qui ont une version antérieure de gazelle-tools pour qu'elles cohabitent avec celles
héritant de gazelle-tools:3.0.25 (à condition que ces dernières utilisent la dernière version d'asm,
cf. ci-dessous).
Dans le fichier jboss-deployment-structure.xml, ajouter le module:
<module name="asm.asm" export="true"/>
Dans le pom.xml de votre projet (le pom parent), ajouter la dépendance:
<dependency>
<groupId>asm</groupId>
<artifactId>asm</artifactId>
<version>3.3.1</version>
<scope>provided</scope>
</dependency>

Je ne saurais que trop vous conseiller, avant de faire votre release, de déployer votre nouvelle
snapshot dans un environnement similaire à celui que sera son environnement de prod (ie copier
les autres ear du jboss de prod en local).
Generated at Sat Apr 15 23:31:38 CEST 2017 using JIRA 7.3.0#73011-
sha1:3c73d0e0b5ea20e2128531b9adf9b0585752b90a.