3 Replies Latest reply on Aug 15, 2014 3:47 PM by Travis Zimmerman

    Unable to launch jbpm-console

    Jose Tafla Newbie

      I've downloaded jBPM 6.0.1 and checked SHA1 to make sure it's right. Next I installed the demo on 3 different environments:

      1. Windows 7
      2. Ubuntu 14.04.1 32 bit
      3. Ubuntu 14.04.1 64 bit

       

      On all 3 I'm experiencing the same issue: after ant install.demo and ant start.demo, going to http://localhost:8080/jbpm-console returns error 404:

      screenshot.1407785723.png

       

      Here's the original jbpm-console.war.failed:

      {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jbpm-console.war\".WeldService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jbpm-console.war\".WeldService: org.jboss.weld.exceptions.DeploymentException: Exception List with 1 exceptions:

      Exception 0 :

      org.jboss.weld.exceptions.WeldException: WELD-000049 Unable to invoke [method] @PostConstruct public org.kie.workbench.backend.AppSetup.assertPlayground() on org.kie.workbench.backend.AppSetup@af820a

        at org.jboss.weld.bean.AbstractClassBean.defaultPostConstruct(AbstractClassBean.java:518)

        at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.postConstruct(ManagedBean.java:174)

        at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:291)

        at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:107)

        at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:90)

        at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)

        at org.kie.workbench.backend.AppSetup$Proxy$_$$_WeldClientProxy.toString(AppSetup$Proxy$_$$_WeldClientProxy.java)

        at org.uberfire.commons.services.cdi.StartupBeanExtension.runPostConstruct(StartupBeanExtension.java:83)

        at org.uberfire.commons.services.cdi.StartupBeanExtension.afterDeploymentValidation(StartupBeanExtension.java:67)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:606)

        at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:264)

        at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52)

        at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137)

        at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:260)

        at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170)

        at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51)

        at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154)

        at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:241)

        at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:229)

        at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207)

        at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)

        at org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:46)

        at org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:31)

        at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:369)

        at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)

        at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

        at java.lang.Thread.run(Thread.java:744)

      Caused by: java.lang.reflect.InvocationTargetException

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:606)

        at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:264)

        at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52)

        at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137)

        at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:260)

        at org.jboss.weld.introspector.jlr.WeldMethodImpl.invoke(WeldMethodImpl.java:174)

        at org.jboss.weld.bean.AbstractClassBean.defaultPostConstruct(AbstractClassBean.java:516)

        ... 33 more

      Caused by: java.lang.NullPointerException

        at org.uberfire.backend.server.organizationalunit.OrganizationalUnitServiceImpl.addRepository(OrganizationalUnitServiceImpl.java:149)

        at org.uberfire.backend.server.organizationalunit.OrganizationalUnitServiceImpl$Proxy$_$$_WeldClientProxy.addRepository(OrganizationalUnitServiceImpl$Proxy$_$$_WeldClientProxy.java)

        at org.jbpm.console.ng.bd.backend.server.AdministrationServiceImpl.bootstrapRepository(AdministrationServiceImpl.java:149)

        at org.jbpm.console.ng.bd.backend.server.AdministrationServiceImpl$Proxy$_$$_WeldClientProxy.bootstrapRepository(AdministrationServiceImpl$Proxy$_$$_WeldClientProxy.java)

        at org.kie.workbench.backend.AppSetup.assertPlayground(AppSetup.java:102)

        ... 43 more

      "}}}}

       

      Next I re-ran ant install.demo, with the same result. Here's the new jbpm-console.war.failed:

      {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"deployment\" => \"jbpm-console.war\")]"}}

       

      Any help is greatly appreciated.

        • 1. Re: Unable to launch jbpm-console
          Travis Zimmerman Newbie

          Your error message looks like it's in the server.log, after installation.  Before that, when you were installing with "ant install.demo", did you check the full ant output to see if there were any errors?  You can use the "-v" option with ant to get verbose output, and then maybe you would see an error.

           

          The second time you ran "ant install.demo", it looks like it failed because the WAR file was already installed.  You can use "ant clean.demo" to go back to a clean state, and then run "ant install.demo" again.

           

          HTH

          • 2. Re: Re: Unable to launch jbpm-console
            Jose Tafla Newbie

            Thank you badtea for your response.

             

            I used ant -v install.demo but the end result was the same. I've included a tarball of the log files.

             

            Thanks again,

            • 3. Re: Unable to launch jbpm-console
              Travis Zimmerman Newbie

              You're right, there doesn't seem to be any errors in your ant logs, so it looks like the installation is OK.

               

              I took another look at the stack trace you posted.  At the bottom there is a NullPointerException when it calls the addRepository() method.  Just guessing by the name of that method, maybe it is trying to create some file(s) somewhere and it does not have permission.  If possible, maybe you could try the installation process as root.  If it works as root, then it must be some kind of permissions issue.

               

              I did not have to install as root when I did it, but that's the only other idea I have for now.

               

              HTH