Re: [rules-users] Drools flow web console (5.1.M1) deployment in JBoss

You pointed out the exact issue. This was what happened. I was using defaultpackage of Guvnor, thinking it refers to the "default". After I created the new package called "default" and uploaded the definition, it worked fine and it did not throw any exception. Kris Verlaenen wrote: > > When you uploaded your sample process to Guvnor, did you add it to the > "default" package (notice that the name should really be "default", and > not "defaultPackage", which is created in Guvnor by default)? And after > adding the process to the package, did you build the package on Guvnor? > > The NPE seems to indicate that it cannot find the knowledge base for > package "default" on Guvnor. > > Kris > > Quoting satjo <jo_satish(a)yahoo.com&gt;: > >> >> Thanks for your response! >> It did fix the problem and I do not get the exception after I log in >> if I >> run org.drools.task.RunTaskService. >> >> I, however, get exception if I click on 'Process >> Definitions'->'Definition >> List'. >> Here is the stack trace. >> >> >> URL: >> 'http://localhost:8080/gwt-console-server/rs/process/definitions' >> Action: >> 'org.jboss.bpm.console.client.process.UpdateDefinitionsAction' >> Exception: 'class com.google.gwt.http.client.RequestException' >> HTTP 500: >> HTTP Status 500 - >> >> > -------------------------------------------------------------------------------- >> >> type Exception report >> >> message >> >> description The server encountered an internal error () that >> prevented it >> from fulfilling this request. >> >> exception >> >> org.jboss.resteasy.spi.UnhandledException: >> java.lang.RuntimeException: Could >> not initialize stateful knowledge session: null >> >> > org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319) >> >> > org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230) >> >> > org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206) >> >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360) >> >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) >> >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) >> >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> >> > org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) >> >> > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) >> >> >> root cause >> >> java.lang.RuntimeException: Could not initialize stateful knowledge >> session: >> null >> >> > org.drools.integration.console.DroolsFlowCommandDelegate.newStatefulKnowledgeSession(DroolsFlowCommandDelegate.java:68) >> >> > org.drools.integration.console.DroolsFlowCommandDelegate.getSession(DroolsFlowCommandDelegate.java:76) >> >> > org.drools.integration.console.DroolsFlowCommandDelegate.<init>(DroolsFlowCommandDelegate.java:35) >> >> > org.drools.integration.console.DroolsFlowProcessManagement.<init>(DroolsFlowProcessManagement.java:20) >> >> > org.drools.integration.console.DroolsFlowManagementFactory.createProcessManagement(DroolsFlowManagementFactory.java:11) >> >> > org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessManagement(ProcessMgmtFacade.java:83) >> >> > org.jboss.bpm.console.server.ProcessMgmtFacade.getDefinitionsJSON(ProcessMgmtFacade.java:107) >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> java.lang.reflect.Method.invoke(Method.java:597) >> >> > org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117) >> >> > org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260) >> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232) >> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166) >> >> > org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142) >> >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) >> >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) >> >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) >> >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> >> > org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) >> >> > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) >> >> >> root cause >> >> java.lang.NullPointerException >> >> > org.drools.agent.impl.KnowledgeAgentImpl.rebuildResources(KnowledgeAgentImpl.java:427) >> >> > org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:120) >> >> > org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:109) >> >> > org.drools.integration.console.DroolsFlowCommandDelegate.newStatefulKnowledgeSession(DroolsFlowCommandDelegate.java:41) >> >> > org.drools.integration.console.DroolsFlowCommandDelegate.getSession(DroolsFlowCommandDelegate.java:76) >> >> > org.drools.integration.console.DroolsFlowCommandDelegate.<init>(DroolsFlowCommandDelegate.java:35) >> >> > org.drools.integration.console.DroolsFlowProcessManagement.<init>(DroolsFlowProcessManagement.java:20) >> >> > org.drools.integration.console.DroolsFlowManagementFactory.createProcessManagement(DroolsFlowManagementFactory.java:11) >> >> > org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessManagement(ProcessMgmtFacade.java:83) >> >> > org.jboss.bpm.console.server.ProcessMgmtFacade.getDefinitionsJSON(ProcessMgmtFacade.java:107) >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> java.lang.reflect.Method.invoke(Method.java:597) >> >> > org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117) >> >> > org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260) >> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232) >> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166) >> >> > org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142) >> >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) >> >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) >> >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) >> >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> >> > org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) >> >> > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) >> >> >> note >> >> >> >> >> Kris Verlaenen wrote: >> > >> > This exception is simply caused by the fact that you don't have a >> human >> > task service installed. So when the console tries to show the >> tasks of >> > the user, or execute a process, it will fail to connect. >> > >> > To start a task service locally: the drools-process-task module >> contains >> > a org.drools.task.RunTaskService class in the src/test/java source >> > folder that can be used to start a task server. >> > >> > I admit that this should be handled in a more user-friendly manner >> > though, I'll see what I can do. >> > >> > Kris >> > >> > Quoting satjo <jo_satish(a)yahoo.com&gt;: >> > >> >> >> >> I have built the war files using the code from SVN and following >> is >> >> the stack >> >> tarce. >> >> I also see a warning in server logs that says 'WARN [PluginMgr] >> >> Unable to >> >> load plugin: >> >> 'org.jboss.bpm.console.server.plugin.ProcessEnginePlugin'. >> >> >> >> Do I need to copy any jar file in JBoss's lib folder >> >> (jboss-4.2.3.GA\server\default\lib)? >> >> >> >> Again, here are steps I followed so far: >> >> >> >> 1.) Downloaded the Standalone Guvnor with JBoss AS. >> >> 2.) Copied gwt-console war files >> >> (gwt-console-server-drools-{version}.war >> >> and gwt-console-drools-{version}.war) in the Standalone download >> >> (jboss-4.2.3.GA\server\default\ldeploy) >> >> 3.) Uploaded a test rule flow in Guvnor's default package and >> rebuilt >> >> it. >> >> 4.) Created the data-source (that got deployed fine), did not >> >> anything for >> >> history or reports configuration to start with. >> >> >> >> JBoss started without any error. When I logged in, I get the >> >> following >> >> error. >> >> >> >> URL: 'http://localhost:8080/gwt-console-server/rs/tasks/admin' >> >> Action: 'org.jboss.bpm.console.client.task.LoadTasksAction' >> >> Exception: 'class com.google.gwt.http.client.RequestException' >> >> HTTP 500: >> >> HTTP Status 500 - >> >> >> >> >> > >> > -------------------------------------------------------------------------------- >> >> >> >> type Exception report >> >> >> >> message >> >> >> >> description The server encountered an internal error () that >> >> prevented it >> >> from fulfilling this request. >> >> >> >> exception >> >> >> >> org.jboss.resteasy.spi.UnhandledException: >> >> java.lang.IllegalArgumentException: Could not connect task client >> >> >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319) >> >> >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230) >> >> >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206) >> >> >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360) >> >> >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) >> >> >> >> >> > >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) >> >> >> >> >> > >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) >> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> >> >> >> >> > >> > org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) >> >> >> >> >> > >> > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) >> >> >> >> >> >> root cause >> >> >> >> java.lang.IllegalArgumentException: Could not connect task client >> >> >> >> >> > >> > org.drools.integration.console.DroolsFlowTaskManagement.connect(DroolsFlowTaskManagement.java:48) >> >> >> >> >> > >> > org.drools.integration.console.DroolsFlowTaskManagement.getAssignedTasks(DroolsFlowTaskManagement.java:128) >> >> >> >> >> > >> > org.jboss.bpm.console.server.TaskListFacade.getTasksForIdRef(TaskListFacade.java:99) >> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> >> >> >> > >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> >> >> >> >> > >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> >> java.lang.reflect.Method.invoke(Method.java:597) >> >> >> >> >> > >> > org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117) >> >> >> >> >> > >> > org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260) >> >> >> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232) >> >> >> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166) >> >> >> >> >> > >> > org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142) >> >> >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) >> >> >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) >> >> >> >> >> > >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) >> >> >> >> >> > >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) >> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> >> >> >> >> > >> > org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) >> >> >> >> >> > >> > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) >> >> >> >> -------------------------------------------------------------- >> >> Following is the Server log >> >> -------------------------------------------------- >> >> 12:31:44,189 WARN [PluginMgr] Unable to load plugin: >> >> 'org.jboss.bpm.console.ser >> >> ver.plugin.ProcessEnginePlugin' >> >> 12:31:46,001 ERROR [[Resteasy]] Servlet.service() for servlet >> >> Resteasy threw >> >> exc >> >> eption >> >> org.jboss.resteasy.spi.UnhandledException: >> >> java.lang.IllegalArgumentException: C >> >> ould not connect task client >> >> at >> >> >> org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationExcept >> >> ion(SynchronousDispatcher.java:319) >> >> at >> >> >> org.jboss.resteasy.core.SynchronousDispatcher.handleException(Synchro >> >> nousDispatcher.java:230) >> >> at >> >> >> org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException( >> >> SynchronousDispatcher.java:206) >> >> at >> >> >> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispa >> >> tcher.java:360) >> >> at >> >> >> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispa >> >> tcher.java:173) >> >> at >> >> >> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.servi >> >> ce(HttpServletDispatcher.java:93) >> >> at >> >> >> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.servi >> >> ce(HttpServletDispatcher.java:68) >> >> at >> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> >> at >> >> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl >> >> icationFilterChain.java:290) >> >> at >> >> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF >> >> ilterChain.java:206) >> >> at >> >> >> org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilte >> >> r.java:59) >> >> at >> >> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl >> >> icationFilterChain.java:235) >> >> at >> >> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF >> >> ilterChain.java:206) >> >> at >> >> >> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi >> >> lter.java:96) >> >> at >> >> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl >> >> icationFilterChain.java:235) >> >> at >> >> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF >> >> ilterChain.java:206) >> >> at >> >> >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV >> >> alve.java:230) >> >> at >> >> >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextV >> >> alve.java:175) >> >> at >> >> >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit >> >> yAssociationValve.java:182) >> >> at >> >> >> org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica >> >> torBase.java:524) >> >> at >> >> >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv >> >> e.java:84) >> >> at >> >> >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j >> >> ava:127) >> >> at >> >> >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j >> >> ava:102) >> >> at >> >> >> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC >> >> onnectionValve.java:157) >> >> at >> >> >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal >> >> ve.java:109) >> >> at >> >> >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav >> >> a:262) >> >> >> >> >> >> >> >> >> >> Kris Verlaenen wrote: >> >> > >> >> > Damn, the DroolsFlowCommandDelegate seems to be swallowing the >> >> > exception, as the exception caught there is not added as the >> root >> >> of the >> >> > thrown exception (line 68). There's no stack trace of a >> >> > NullPointerException in the log (right) before this error? >> >> > >> >> > I also fixed this on trunk, so the caught NullPointerException >> is >> >> added >> >> > as the root cause now, so the stack trace should now contain the >> >> trace >> >> > of the NPE as well. If there's no NPE in the log, could you >> update >> >> your >> >> > code from SVN, rebuild the wars, try again and send me the stack >> >> trace >> >> > again? >> >> > >> >> > Kris >> >> > >> >> > Quoting satjo <jo_satish(a)yahoo.com&gt;: >> >> > >> >> >> >> >> >> I have set the data source. Following is the stack trace. >> >> >> >> >> >> When I go to Settings->System->Overview, I see that >> >> >> org.jboss.bpm.console.server.plugin.ProcessEnginePlugin is not >> >> green. >> >> >> >> >> >> I must have missed something in the installation or copying a >> >> >> dependant jar >> >> >> file. >> >> >> >> >> >> >> >> >> URL: >> >> >> >> 'http://localhost:8080/gwt-console-server/rs/process/definitions' >> >> >> Action: >> >> >> 'org.jboss.bpm.console.client.process.UpdateDefinitionsAction' >> >> >> Exception: 'class com.google.gwt.http.client.RequestException' >> >> >> HTTP 500: >> >> >> HTTP Status 500 - >> >> >> >> >> >> >> >> > >> >> >> > >> > -------------------------------------------------------------------------------- >> >> >> >> >> >> type Exception report >> >> >> >> >> >> message >> >> >> >> >> >> description The server encountered an internal error () that >> >> >> prevented it >> >> >> from fulfilling this request. >> >> >> >> >> >> exception >> >> >> >> >> >> org.jboss.resteasy.spi.UnhandledException: >> >> >> java.lang.RuntimeException: Could >> >> >> not initialize stateful knowledge session: null >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) >> >> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) >> >> >> >> >> >> >> >> >> root cause >> >> >> >> >> >> java.lang.RuntimeException: Could not initialize stateful >> >> knowledge >> >> >> session: >> >> >> null >> >> >> >> >> >> >> >> > >> >> >> > >> > org.drools.integration.console.DroolsFlowCommandDelegate.newStatefulKnowledgeSession(DroolsFlowCommandDelegate.java:69) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.drools.integration.console.DroolsFlowCommandDelegate.getSession(DroolsFlowCommandDelegate.java:77) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.drools.integration.console.DroolsFlowCommandDelegate.<init>(DroolsFlowCommandDelegate.java:35) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.drools.integration.console.DroolsFlowProcessManagement.<init>(DroolsFlowProcessManagement.java:20) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.drools.integration.console.DroolsFlowManagementFactory.createProcessManagement(DroolsFlowManagementFactory.java:11) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessManagement(ProcessMgmtFacade.java:83) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.bpm.console.server.ProcessMgmtFacade.getDefinitionsJSON(ProcessMgmtFacade.java:107) >> >> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> >> >> >> >> >> >> > >> >> >> > >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> >> >> >> >> >> >> >> > >> >> >> > >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> >> >> java.lang.reflect.Method.invoke(Method.java:597) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260) >> >> >> >> >> >> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232) >> >> >> >> >> >> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) >> >> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) >> >> >> >> >> >> >> >> > >> >> >> > >> > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Kris Verlaenen wrote: >> >> >> > >> >> >> > Did you configure the data source correctly? >> >> >> > >> >> >> >> >> > >> >> >> > >> > https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/t... >> >> >> > >> >> >> > The full stack trace of the error that should be visible in >> the >> >> >> server >> >> >> > console could help to identify the issue as well. >> >> >> > >> >> >> > Kris >> >> >> > >> >> >> > Quoting satjo <jo_satish(a)yahoo.com&gt;: >> >> >> > >> >> >> >> >> >> >> >> Could some one share the experience in getting the Drools >> Flow >> >> 5.1 >> >> >> >> web >> >> >> >> console working in JBoss? >> >> >> >> >> >> >> >> I downloaded the “Standalone Guvnor >> with JBoss >> >> AS” >> >> >> (Drools >> >> >> >> 5.1.0.M1 Guvnor >> >> >> >> Standalone) from the download site. >> >> >> >> >> >> >> >> As it did not have the gwt-console war files >> >> >> >> (gwt-console-server-drools-{version}.war and >> >> >> >> gwt-console-drools-{version}.war) in the Standalone >> download, I >> >> >> built >> >> >> >> them >> >> >> >> from source code and deployed in JBoss. >> >> >> >> >> >> >> >> I uploaded a test rule flow in >> Guvnor’s default >> >> package and >> >> >> rebuilt >> >> >> >> the >> >> >> >> package. >> >> >> >> >> >> >> >> After log into gwt-console, when I click on process >> >> definition, I >> >> >> >> see a >> >> >> >> HTTP 500 error ‘class >> >> >> com.google.gwt.http.client.RequestException', >> >> >> >> ‘ Could >> >> >> >> not initialize stateful knowledge session: >> null’. >> >> >> >> >> >> >> >> Any comments on the required steps for viewing the process >> >> >> >> definitions are >> >> >> >> appreciated. >> >> >> >> >> >> >> >> satjo >> >> >> >> -- >> >> >> >> View this message in context: >> >> >> >> >> >> >> > >> >> >> >> >> > >> >> >> > >> > http://www.nabble.com/Drools-flow-web-console-%285.1.M1%29-deployment-in-... >> >> >> >> Sent from the drools - user mailing list archive at >> Nabble.com. >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> rules-users mailing list >> >> >> >> rules-users(a)lists.jboss.org >> >> >> >> https://lists.jboss.org/mailman/listinfo/rules-users >> >> >> >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm >> >> >> > _______________________________________________ >> >> >> > rules-users mailing list >> >> >> > rules-users(a)lists.jboss.org >> >> >> > https://lists.jboss.org/mailman/listinfo/rules-users >> >> >> > >> >> >> > >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> > >> >> >> > >> > http://www.nabble.com/Drools-flow-web-console-%285.1.M1%29-deployment-in-... >> >> >> Sent from the drools - user mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> rules-users mailing list >> >> >> rules-users(a)lists.jboss.org >> >> >> https://lists.jboss.org/mailman/listinfo/rules-users >> >> >> >> >> > >> >> > >> >> > >> >> > >> >> > Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm >> >> > _______________________________________________ >> >> > rules-users mailing list >> >> > rules-users(a)lists.jboss.org >> >> > https://lists.jboss.org/mailman/listinfo/rules-users >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> > >> > http://www.nabble.com/Drools-flow-web-console-%285.1.M1%29-deployment-in-... >> >> Sent from the drools - user mailing list archive at Nabble.com. >> >> >> >> >> >> _______________________________________________ >> >> rules-users mailing list >> >> rules-users(a)lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/rules-users >> >> >> > >> > >> > >> > >> > Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm >> > _______________________________________________ >> > rules-users mailing list >> > rules-users(a)lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/rules-users >> > >> > >> >> -- >> View this message in context: >> > http://www.nabble.com/Drools-flow-web-console-%285.1.M1%29-deployment-in-... >> Sent from the drools - user mailing list archive at Nabble.com. >> >> >> _______________________________________________ >> rules-users mailing list >> rules-users(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/rules-users >> > > > > > Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > >