6 Replies Latest reply on Mar 28, 2006 11:40 AM by Aaron DeLong

    Issues with deploying BPEL example

    Juha Särkinen Newbie

      Hi,

      I'm trying to deploy the hello example process from the jbpm-BPEL-alpha4 package. This is what I've done:

      1. Install jbpm-starters-kit-3.1 (works fine)
      2. unzip the jbpm-bpel-alpha4.zip to jbpm-bpel directory
      3. change the build.properties in the bpel home directory
      4. execute "ant build.service.402" (Build successful)
      5. deploy the jbpm-bpel.sar to jboss
      6. alter the build.properties from the hello example directory
      7. execute "ant create-schema" (Build successful)
      8. execute "ant pack-definition" (Build successful)
      9. execute "ant deploy-definition" and this is where things go wrong.

      Buildfile: build.xml
      
      pack-definition:
      
      deploy-definition:
      [webdeploy] deployment url: http://kanno:8080/jbpm-bpel/deploy?archive=file%3A%2
      FP%3A%2Fdownload%2Fjbpm-starters-kit-3.1%2Fjbpm-bpel%2Fdoc%2Fexamples%2Fhello%2F
      build%2Fhello-definition.par
      [webdeploy] got response code: 500
      
      BUILD FAILED
      P:\download\jbpm-starters-kit-3.1\jbpm-bpel\doc\examples\hello\build.xml:97: deployment failed, see details in the server console
      
      Total time: 8 seconds


      and the JBOSS console says:

      15:26:34,819 INFO [[/jbpm-bpel]] DeployServlet: deploying process archive: file:/P:/download/jbpm-starters-kit-3.1/jbpm-bpel/doc/examples/hello/build/hello-definition.par
      15:26:34,834 ERROR [[DeployServlet]] Servlet.service() for servlet DeployServlet threw exception
      org.jbpm.jpdl.JpdlException: [[ERROR] no processdefinition.xml inside process archive]
       at org.jbpm.jpdl.par.JpdlArchiveParser.readFromArchive(JpdlArchiveParser.java:39)
       at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:81)
       at org.jbpm.bpel.web.deploy.DeployServlet.doGet(DeployServlet.java:45)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
       at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
       at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
       at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
       at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
       at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
       at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
       at java.lang.Thread.run(Thread.java:595)
      


      I interpret that this error means that there is no processdefinition.xml in the hello-definition.par.
      I checked and there is bpel-definition.xml in the par-file.
      Then I tried to change its file name to processdefinition.xml and alter the build.xml to match it.
      Still the error occurs.

      Can anyone help me?

      Juha S.


        • 1. Re: Issues with deploying BPEL example
          Juha Särkinen Newbie

          Has anyone a clue? I'm doing this for an university student project, where we inspect currently available open source BPM systems. The aim is to produce a report on the features of these, and make a recommendation. This report is probably later used by some companies, who need to select such a system for their process management tool. An important requirement for this system is that it is possible to deploy a bpel process in it. We aren't very experienced in technical field, our task is just to get this system up and running with a BPEL process in it.

          • 2. Re: Issues with deploying BPEL example
            Alejandro Guizar Master

            The application server configuration included in the starters kit does not include the web services module and therefore cannot be used for deploying the BPEL service archive. Use a standard JBoss distribution rather than the jBPM starters kit.

            • 3. Re: Issues with deploying BPEL example
              Juha Särkinen Newbie

              Thanks for the reply!
              But still I'm stuck... Now I've installed the JBOSS 4.0.3 SP1.
              The BPEL-tutorial says that I have to execute "ant build.service.403".
              It produces the jbpm-bpel.sar and when I copy it to the JBOSS/server/default/deploy directory, the JBOSS console says:

              11:12:36,597 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss/se
              rver/default/deploy/jbpm-bpel.sar
              org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jbpm.db
              .jmx.JbpmService; - nested throwable: (java.lang.ClassNotFoundException: No Clas
              sLoaders found for: org.jbpm.db.jmx.JbpmService)
               at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
              :178)
               at org.jboss.system.ServiceController.install(ServiceController.java:215
              )
               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
               at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
              java:39)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
              sorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:585)
               at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
              er.java:141)
               at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
               at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
              java:245)
               at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
               at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
               at $Proxy4.install(Unknown Source)
               at org.jboss.deployment.SARDeployer.create(SARDeployer.java:232)
               at org.jboss.deployment.MainDeployer.create(MainDeployer.java:935)
               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:789)
               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
               at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
              java:39)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
              sorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:585)
               at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
              er.java:141)
               at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
               at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
              or.java:118)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
               at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
              BeanOperationInterceptor.java:127)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
               at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
              java:245)
               at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
               at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
               at $Proxy9.deploy(Unknown Source)
               at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
              tScanner.java:319)
               at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
              canner.java:507)
               at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
              doScan(AbstractDeploymentScanner.java:192)
               at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
              bstractDeploymentScanner.java:265)
               at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
              upport.java:274)
               at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
              eanSupport.java:230)
               at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
              sorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:585)
               at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
              er.java:141)
               at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
               at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
              java:245)
               at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
               at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
              ler.java:943)
               at $Proxy0.start(Unknown Source)
               at org.jboss.system.ServiceController.start(ServiceController.java:428)
               at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
              sorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:585)
               at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
              er.java:141)
               at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
               at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
              java:245)
               at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
               at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
               at $Proxy4.start(Unknown Source)
               at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)
               at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
               at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
               at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
              java:39)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
              sorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:585)
               at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
              er.java:141)
               at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
               at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
              or.java:118)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
               at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
              BeanOperationInterceptor.java:127)
               at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
               at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
              java:245)
               at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
               at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
               at $Proxy5.deploy(Unknown Source)
               at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453)
               at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330)
               at org.jboss.Main.boot(Main.java:187)
               at org.jboss.Main$1.run(Main.java:438)
               at java.lang.Thread.run(Thread.java:595)
              Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jbpm
              .db.jmx.JbpmService
               at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:198)
               at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryCl
              assLoader.java:475)
               at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassL
              oader.java:377)
               at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
               at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:
              1189)
               at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:
              271)
               at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:
              329)
               at org.jboss.system.ServiceCreator.install(ServiceCreator.java:124)
               at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigura
              tor.java:431)
               at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
              :153)
               ... 81 more


              and finally:

              11:13:01,433 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
              
              --- Incompletely deployed packages ---
              org.jboss.deployment.DeploymentInfo@c342ccef { url=file:/C:/jboss/server/default
              /deploy/jbpm-bpel.sar }
               deployer: org.jboss.deployment.SARDeployer@18941f7
               status: Deployment FAILED reason: No ClassLoaders found for: org.jbpm.db.jmx.J
              bpmService; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoade
              rs found for: org.jbpm.db.jmx.JbpmService)
               state: FAILED
               watch: file:/C:/jboss/server/default/deploy/jbpm-bpel.sar
               altDD: null
               lastDeployed: 1142932356577
               lastModified: 1142932355526
               mbeans:
              
              
              11:13:01,633 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-808
              0
              11:13:01,864 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
              11:13:01,874 INFO [JkMain] Jk running ID=0 time=0/80 config=null
              11:13:01,894 INFO [Server] JBoss (MX MicroKernel) [4.0.3SP1 (build: CVSTag=JBos
              s_4_0_3_SP1 date=200510231054)] Started in 45s:345ms
              


              Why the .sar file cannot be deployed? What is the meaning of No ClassLoaders Found?

              I'm using:
              JBOSS 4.0.3 (with the default server configuration)
              jBPM 3.1
              jBPM BPEL 1.0 alpha4
              default Hypersonic SQL database.

              Thanks!
              Juha S.

              • 4. Re: Issues with deploying BPEL example
                Alejandro Guizar Master

                Did you replace the jBPM 3.0.2 library bundled with BPEL alpha 4 with jBPM 3.1? This won't work! Please use the default library. The upcoming beta 1 supports jBPM 3.1.

                • 5. Re: Issues with deploying BPEL example
                  Juha Särkinen Newbie

                  Thanks for the reply! I didn't know alpha4 is not compatible with jBPM 3.1. Now the sar-file is deployed succesfully and the problem is solved.

                  Juha S.

                  • 6. Re: Issues with deploying BPEL example
                    Aaron DeLong Newbie

                    2 questions...

                    1_How can I tell which version of the JBPM is installed?
                    2_Will this install work with AS 4.0.4RC1?