BPM Spring integration fails on Tomcat with PER_PROCESS_INSTANCE strategy

Solution Verified - Updated -

Issue

Server fail starting when PER_PROCESS_INSTANCE is defined in applicationContext.xml. This issue occurs when PER_PROCESS_INSTANCE is used in Spring Environment with not JTA server. Stacktrace includes following message:

java.lang.IllegalStateException: Unable to find transaction: Cannot create resource instance
    org.drools.persistence.jta.JtaTransactionManager.findUserTransaction(JtaTransactionManager.java:140)
    org.drools.persistence.jta.JtaTransactionManager.<init>(JtaTransactionManager.java:79)
    org.jbpm.runtime.manager.impl.AbstractRuntimeManager.registerDisposeCallback(AbstractRuntimeManager.java:113)
    org.jbpm.runtime.manager.impl.PerProcessInstanceRuntimeManager.getRuntimeEngine(PerProcessInstanceRuntimeManager.java:112)

Environment

  • Red Hat JBoss BPM Suite
    • 6.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content