3 Replies Latest reply on Dec 30, 2011 6:02 PM by tsurdilovic

    Unable to see Process in Process Overview

    murthy516

      Hi All,

       

      I copied .bpmn file to Jbpm installer/sample/evaluation folder.But,when I'm opening JBPM console it is generating error as

       

      16:58:40,668 ERROR [[Resteasy]] Servlet.service() for servlet Resteasy threw exception

      org.jboss.resteasy.spi.UnhandledException: java.lang.IllegalArgumentException: Could not connect task client

              at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319)

              at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230)

              at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206)

              at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360)

              at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173)

              at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93)

              at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68)

              at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

              at org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

              at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

              at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)

              at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

              at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)

              at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)

              at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)

              at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValv

      a:126)

              at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve

      :70)

              at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

              at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

              at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)

              at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

              at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)

              at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)

              at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)

              at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)

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

      Caused by: java.lang.IllegalArgumentException: Could not connect task client

              at org.jbpm.integration.console.TaskManagement.connect(TaskManagement.java:66)

              at org.jbpm.integration.console.TaskManagement.getAssignedTasks(TaskManagement.java:179)

              at org.jboss.bpm.console.server.TaskListFacade.getTasksForIdRef(TaskListFacade.java:99)

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

              at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117)

              at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260)

              at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232)

              at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166)

              at org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142)

              at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)

              ... 28 more

       

      Please suggest me how to achieve opening JBPM 5console..

        • 1. Re: Unable to see Process in Process Overview
          tsurdilovic

          Your post indicates: "

           

          • 2. Re: Unable to see Process in Process Overview
            murthy516

            Thanks for your reply Surdilovic.I'm using JBPM 5.I have jbpm-installer folder in D:\ drive,where there is jboss-5.1.0.GA in jbpm installer folder.I'm facing this issue whenever I open the JBPM console.Please suggest me.

             

            Thanks

            • 3. Re: Unable to see Process in Process Overview
              tsurdilovic

              I'm guessing here, probably your server startup timed out. One question tho, if you are starting off with jBPM you should start using version 5.2. In 5.2 we moved the default AS to AS7 which starts up a lot faster than AS 5.1 used in jBPM 5.1 and you should not run into timeouts for server startup.