1 Reply Latest reply on Jul 3, 2014 6:40 AM by inspector

    Migration issue from Jboss 7.1.1 to EAP 6.2

    mbsakho
    mbsakho Jun 26, 2014 10:04 AM

      Hi all,

      I have a web service application that works fine when deployed to JBOSS 7.1.1 Final.

      I'm trying to operate the migration to EAP 6.2 but it fails at deployment time with the errors below:

      14:30:01,079 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."ENBWS.ear"."ENBWS-250-ELO.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."ENBWS.ear"."ENBWS-250-ELO.war".INSTALL: JBAS018733: N'a pas pu traiter la phase INSTALL de subdeployment "ENBWS-250-ELO.war" of deployment "ENBWS.ear"

      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

      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.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_11]

      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_11]

      at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]

      Caused by: javax.xml.ws.WebServiceException: org.apache.cxf.bus.extension.ExtensionException: Could not create object of extension class org.apache.cxf.wsdl11.WSDLManagerImpl.

      at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:371)

      at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66)

      at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251)

      at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539)

      at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:117)

      at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129)

      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.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

      ... 5 more

      Caused by: org.apache.cxf.bus.extension.ExtensionException: Could not create object of extension class org.apache.cxf.wsdl11.WSDLManagerImpl.

      at org.apache.cxf.bus.extension.Extension.load(Extension.java:249)

      at org.apache.cxf.bus.extension.ExtensionManagerImpl.loadAndRegister(ExtensionManagerImpl.java:211)

      at org.apache.cxf.bus.extension.ExtensionManagerImpl.getBeansOfType(ExtensionManagerImpl.java:320)

      at org.apache.cxf.bus.CXFBusImpl.getExtension(CXFBusImpl.java:108)

      at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.isEmptywsdl(ReflectionServiceFactoryBean.java:2607)

      at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.isFromWsdl(ReflectionServiceFactoryBean.java:543)

      at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:547)

      at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:265)

      at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:204)

      at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:102)

      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:456)

      at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:334)

      ... 13 more

      Caused by: java.lang.ClassCastException: class org.apache.cxf.binding.corba.wsdl.PolicyType

      at java.lang.Class.asSubclass(Class.java:3037) [rt.jar:1.7.0_11]

      at org.apache.cxf.wsdl.JAXBExtensionHelper.addExtensions(JAXBExtensionHelper.java:91)

      at org.apache.cxf.wsdl11.WSDLManagerImpl.registerInitialXmlExtensions(WSDLManagerImpl.java:304)

      at org.apache.cxf.wsdl11.WSDLManagerImpl.registerInitialExtensions(WSDLManagerImpl.java:274)

      at org.apache.cxf.wsdl11.WSDLManagerImpl.<init>(WSDLManagerImpl.java:126)

      at org.apache.cxf.wsdl11.WSDLManagerImpl.<init>(WSDLManagerImpl.java:94)

      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_11]

      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_11]

      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_11]

      at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [rt.jar:1.7.0_11]

      at org.apache.cxf.bus.extension.Extension.load(Extension.java:240)

      ... 26 more

       

      The same problem has been reported here

       

      Web services exception

       

      Can someone tells me how to resolve this problem

       

      Massai

      • 1101 Views
      • Tags:
        • 1. Re: Migration issue from Jboss 7.1.1 to EAP 6.2
          inspector
          inspector Jul 3, 2014 6:40 AM (in response to mbsakho)

          I'm not sure about your special case. But I've experienced different class casting issues when migrating from JBoss 7.1.1 to EAP 6.2. I had a case where a joda-time object was put into an infinispan cache and when it was taken out again there was a ClassCastException. The maven scope of joda-time was already provided. I made it work by changing the referenced version number from 1.6.2 to 1.6.2-redhat-4 and more importantly by not only referencing joda-time in the manifest of the top-level deployment but in all manifests with something like

              <build>

                  <plugins>

                      <plugin>

                          <artifactId>maven-jar-plugin</artifactId>

           

           

                          <configuration>

                              <archive combine.children="append">

                                  <manifestEntries>

                                      <Dependencies>org.joda.time</Dependencies>

                                  </manifestEntries>

                              </archive>

                          </configuration>

                      </plugin>

                  </plugins>

              </build>

          Maybe your problem is similar but with some cxf related library.

           

          I'm still confused about what in jboss-modules has been changed to cause that issue and what version of it is "buggy" - the eap or the community (I guess the latter).

            • Actions