[jboss-user] [JBoss jBPM] - Bizarro jBPMException when trying to create a new JbpmContex
I am using jBPM 3.1.2, and have incorporated my own servlets into what is basically the
jbpm.war webapp. My servlets start by doing nothing more complicated than create a
jbpmContext, using the following code:
| JbpmConfiguration jc = JbpmConfiguration.getInstance();
| JbpmContext jbpmContext = jc.createJbpmContext();
This code results in this exception:
| org.jbpm.JbpmException: closed JbpmContext in different order then they were
created... check your try-finally's around JbpmContexts blocks
| at org.jbpm.JbpmConfiguration.popJbpmContext(JbpmConfiguration.java:525)
| at org.jbpm.JbpmConfiguration.jbpmContextClosed(JbpmConfiguration.java:537)
| at org.jbpm.JbpmContext.close(JbpmContext.java:144)
| at org.jbpm.web.JbpmContextFilter.doFilter(JbpmContextFilter.java:85)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:65)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| 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.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| 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:869)
| at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| 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)
|
This is bizarre. The only thing my webapp does after loading is what the jbpm.war does by
default, which is start the JbpmThreadsServlet. Does anyone have any idea why this is
happening?
Thanks,
Brad
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969872#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...