[jboss-user] [jBPM] - Re: JBPM5 compatibility with Tomcat and Maven

Anand Prakash [http://community.jboss.org/people/anandintouch] created the discussion "Re: JBPM5 compatibility with Tomcat and Maven" To view the discussion, visit: http://community.jboss.org/message/577577#577577 -------------------------------------------------------------- Hi Kris, I'm able to deploy both the wars on tomcat/webapps and I'm able  to start application(jbpm-console) from browser.I've changed port to  9999 in server.xml instead od 8080.Accordingly changed port in  jbpm-gwt-core properties file. So once I login to the application and when I click Process Overview,then I get exception.It doesn't load the processes. Here is the exception captured from the browser,since I didn't see any log folder in tomcat as it was in Jboss default folder. Error- h1. 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: javax/persistence/Persistence      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:729)      org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) *note* The full stack trace of the root cause is available in the Apache Tomcat/5.5.31 logs. ------------------------------------------------------------------------ Please  let me know if any context.xml change/configuration or setting is  required,because it's not able to find data from the backend. I believe we need to modify context.xml and put somewhere in META-INF. Any help would be greatly appreciated. Thanks, Anand -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/577577#577577] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]