3 Replies Latest reply on Apr 30, 2014 4:35 AM by Jorge Morales

    Is SwitchYard 1.1.1 supposed to work on JBoss EAP 6.1?

    Artem Egorkine Newbie

      Hi,

       

      I compiled Switchyard 1.1.1-p6 and installed it on JBoss EAP 6.1. Deploying an application with CDI beans failed with the following error:

      15:41:33,086 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/victor/ESB/jboss-eap-6.1/standalone/deployments
      15:41:33,091 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "MyESB-0.0.1-SNAPSHOT.war" (runtime-name: "MyESB-0.0.1-SNAPSHOT.war")
      15:41:33,249 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
      15:41:35,567 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'moduleName=groovy-all' for service type 'org.codehaus.groovy.runtime.ExtensionModule'
      15:41:35,567 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'moduleVersion=2.0.5' for service type 'org.codehaus.groovy.runtime.ExtensionModule'
      15:41:35,568 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'extensionClasses=org.codehaus.groovy.jsr223.ScriptExtensions,org.codehaus.groovy.runtime.SqlGroovyMethods,org.codehaus.groovy.runtime.SwingGroovyMethods,org.codehaus.groovy.runtime.XmlGroovyMethods' for service type 'org.codehaus.groovy.runtime.ExtensionModule'
      15:41:35,568 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'staticExtensionClasses=org.codehaus.groovy.jsr223.ScriptStaticExtensions' for service type 'org.codehaus.groovy.runtime.ExtensionModule'
      15:41:36,233 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment MyESB-0.0.1-SNAPSHOT.war
      15:41:36,333 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."MyESB-0.0.1-SNAPSHOT.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."MyESB-0.0.1-SNAPSHOT.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "MyESB-0.0.1-SNAPSHOT.war"
        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.runWorker(ThreadPoolExecutor.java:1146) [rt.jar:1.6.0_27]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.6.0_27]
        at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_27]
      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.ClassNotFoundException: org.jboss.as.weld.deployment.WeldPortableExtensions from [Module "deployment.MyESB-0.0.1-SNAPSHOT.war:main" from Service Module Loader]
        at org.switchyard.as7.extension.deployment.SwitchYardCdiIntegrationProcessor.checkExtension(SwitchYardCdiIntegrationProcessor.java:83)
        at org.switchyard.as7.extension.deployment.SwitchYardCdiIntegrationProcessor.deploy(SwitchYardCdiIntegrationProcessor.java:59)
        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
      Caused by: java.lang.ClassNotFoundException: org.jboss.as.weld.deployment.WeldPortableExtensions from [Module "deployment.MyESB-0.0.1-SNAPSHOT.war:main" from Service Module Loader]
        at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final-redhat-1]
        at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final-redhat-1]
        at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final-redhat-1]
        at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final-redhat-1]
        at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final-redhat-1]
        at org.switchyard.as7.extension.deployment.SwitchYardCdiIntegrationProcessor.checkExtension(SwitchYardCdiIntegrationProcessor.java:71)
        ... 7 more
      
      15:41:36,389 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "MyESB-0.0.1-SNAPSHOT.war" (runtime-name : "MyESB-0.0.1-SNAPSHOT.war")
      15:41:36,393 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
      JBAS014777:   Services which failed to start:      service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
            service jboss.deployment.unit."MyESB-0.0.1-SNAPSHOT.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."MyESB-0.0.1-SNAPSHOT.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "MyESB-0.0.1-SNAPSHOT.war"
      

       

      If you ignore the groovy warnings, I'm left with ClassNotFound exception for the org.jboss.as.weld.deployment.WeldPortableExtensions class. Google suggests that it is a part of wildfly-weld package, which has no place in EAP 6.1. The culprit here comes from https://github.com/jboss-switchyard/release/pull/319 pull request for issue https://issues.jboss.org/browse/SWITCHYARD-1850, which refers to fixing deployment on JBoss EAP 6.1.1. If I revert the pull request commit, I am able to deploy on JBoss EAP 6.1. This poses a question, if SY 1.1.1 is even supposed to be deployable on JBoss EAP 6.1, or am I better off patching 1.1.0.Final version for my own needs (rather than 1.1.1 from 1.x branch)?