6 Replies Latest reply on Mar 2, 2012 11:23 AM by Vishal Changrani

    Problems with JBoss Portal and JBossESB on same JBossAS?

    Janne Mattila Newbie

      I am trying to install JBossESB. I can deploy fine as long as my JBossAS 2.4.1-GA does not have Portal installed yet. But when I try the JBossESB deployment after portal has already been deployed, I get:

      15:14:29,000 WARN [ServiceController] Problem starting service jboss.esb:deployment=jbossesb.esb
      java.lang.NoClassDefFoundError: org/apache/xmlbeans/XmlException
       at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:97)
       at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:82)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
       at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
       at $Proxy0.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:417)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy4.start(Unknown Source)
       at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy192.start(Unknown Source)
       at org.jboss.deployment.XSLSubDeployer.start(XSLSubDeployer.java:197)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
       at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy9.deploy(Unknown Source)
       at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
       at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
       at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:26
      3)
       at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
      
       at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
      15:14:30,781 INFO [JBoss4ESBDeployer] create esb service, jbpm.esb
      15:14:30,781 WARN [ServiceController] Problem starting service jboss.esb:service=JbpmService
      java.lang.NoSuchMethodError: org.jbpm.JbpmConfiguration.getJobExecutor()Lorg/jbpm/job/executor/JobExecutor;
       at org.jboss.soa.esb.services.jbpm.configuration.JbpmService.startService(JbpmService.java:42)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
       at $Proxy0.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:417)
       at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy4.start(Unknown Source)
       at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
       at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)


        • 1. Re: Problems with JBoss Portal and JBossESB on same JBossAS?
          Kevin Conner Master

           

          "jimpo" wrote:
          java.lang.NoClassDefFoundError: org/apache/xmlbeans/XmlException

          This should come from jbossesb.sar/lib/xbean.jar, is this jar present? Does this jar exist elsewhere on your system?

          "jimpo" wrote:
          java.lang.NoSuchMethodError: org.jbpm.JbpmConfiguration.getJobExecutor()Lorg/jbpm/job/executor/JobExecutor;

          This is because the portal includes a very old version of jBPM and this version has been loaded in preference to the version we are using.


          • 2. Re: Problems with JBoss Portal and JBossESB on same JBossAS?
            Janne Mattila Newbie

            Going to update this thread also, to let other people with similar problem see what my solution was. Thanks Kevin for the info.

            "Kevin.Conner@jboss.com" wrote:
            "jimpo" wrote:
            java.lang.NoClassDefFoundError: org/apache/xmlbeans/XmlException

            This should come from jbossesb.sar/lib/xbean.jar, is this jar present? Does this jar exist elsewhere on your system?


            Not sure, I am however installing the esb the exact same way I do when I install it on a "blank" JBossAS without portal. And in that case I get no errors from missing XMLException class.

            "Kevin.Conner@jboss.com" wrote:

            "jimpo" wrote:
            java.lang.NoSuchMethodError: org.jbpm.JbpmConfiguration.getJobExecutor()Lorg/jbpm/job/executor/JobExecutor;

            This is because the portal includes a very old version of jBPM and this version has been loaded in preference to the version we are using.


            The way to go seems to be that I will have a separate JBossAS instance for my portal and a separate one for the ESB, as they can't coexist on same JBossAS without problems.

            • 3. Re: Problems with JBoss Portal and JBossESB on same JBossAS?
              Kevin Conner Master

               

              "jimpo" wrote:
              Not sure, I am however installing the esb the exact same way I do when I install it on a "blank" JBossAS without portal. And in that case I get no errors from missing XMLException class.

              I can't think of any reason why the presence of portal should cause this issue, the whole sar should have been copied across to the deploy directory. This one is puzzling.

              "jimpo" wrote:
              The way to go seems to be that I will have a separate JBossAS instance for my portal and a separate one for the ESB, as they can't coexist on same JBossAS without problems.

              This is the safest solution at present, apologies for this. We have raised the jBPM version conflict as an issue and are trying to get it addressed.

              Kev

              • 4. Re: Problems with JBoss Portal and JBossESB on same JBossAS?
                Vishal Changrani Newbie

                Any updates to this?

                Is there a way to tell jboss to us a different jar for jbpm than what might be in the application EAR?

                • 5. Re: Problems with JBoss Portal and JBossESB on same JBossAS?
                  Tom Cunningham Master

                  Can you give us some details what you are seeing, and what versions of AS/Portal/ESB you are using?

                  • 6. Re: Problems with JBoss Portal and JBossESB on same JBossAS?
                    Vishal Changrani Newbie

                    Hi Tom,

                    Thanks for replying. And forgive my naievity..am new to JBOSS....

                    My ESB Version is 1.0.1 as per the jboss-esb.xml.

                    My JBOSS version is 5.1.0.

                    More details of the configuration to follow soon....

                    For some reason when JBOSS comes up I see the error mentioned above (java.lang.NoSuchMethodError: org.jbpm.JbpmConfiguration.getJobExecutor()Lorg/jbpm/job/executor/JobExecutor;)

                    I realized this is because of an older version of jbpm getting loaded. This older version is coming from the lib folder of our ear and it depends on this older version. So I tried to localize and isolate the jars loaded by ESB and JBPM services by putting in the

                    XML elements,

                    <loader-repository>
                        com.example:loader=jbossesb/jbossjbpm
                        <loader-repository-config>
                            java2ParentDelegation=false
                        </loader-repository-config>
                    </loader-repository>

                    but that didnt help.

                    Then I observed there is a ..jboss/server/standard/deployers/esb.deployer folder which might be loading the jbpm jar from my application. So I put the correct jbom (jbpm-jpdl.jar) in the lib folder under this deployer. I got over the above mentioned issue but now it complains -  org.jbpm.configuration.ConfigurationException: name 'jbpm.job.executor' is not defined in the configuration. configured names: [jbpm.task.instance.factory,......

                    The org.jbpm.executor is indeed defined in jbpm.cfg.xml in the deploy/jbpm.esb folder.

                     

                    Will appreciate any light you can shed or point me in the right direction.

                    thanks.