Need help with EJB3 and jBPM 3.1 transactions on JBoss 4.0.4

[j.hedin]

Hi all

I can't get transaction propagation to work with EJB3-RC5, JBoss 4.0.4RC1 and jBPM 3.1. The senario that troubles me is the case where the start of the transaction is in EJB3 SLSB -> token.signal() -> call to the sam EJB3 SLSB (new lookup). I get an error

2006-04-11 16:21:51,179 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Error: 0, SQLState: null
2006-04-11 16:21:51,179 ERROR [org.hibernate.util.JDBCExceptionReporter] Transaction is not active: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=doloxene.sth.ecare.se/111, BranchQual=, localId=111]; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=doloxene.sth.ecare.se/111, BranchQual=, localId=111])

The jBPM class looks like this

/**
 * jBPM action for inserting a message from RIS into the DB. The node propagates the
 * process execution further after inserting the message
 * @version $Id$
 */
public class InsertMessage implements ActionHandler {

 protected static Logger logger = Logger.getLogger(InsertMessage.class);

 public void execute(ExecutionContext executionContext) throws Exception {

 if(logger.isDebugEnabled()) {
 logger.debug("Executing inserting messages");
 }
 String tmPK = (String)executionContext.getVariable(IBConstants.TRANSIENT_MESSAGE_ID_VARIABLE);
 Context context = new InitialContext();
 if(logger.isDebugEnabled()) {
 logger.debug("About to insert message from TransientMessage with id "+ tmPK);
 }
 RISInputManagement rm = (RISInputManagement)context.lookup(RISInputManagement.class.getName());
 rm.insertMessageById(tmPK);
 executionContext.leaveNode();
 }
}

The EntityManager is injected in the SLSB. jBPM is configurated to disable transactions and the underlaying Hibernate to use JTA transactions. Any clues?



Thanks In Advance

Johan Hedin

[j.hedin]

I have the same result with JBoss 4.0.4.CR2

[koen.aers]

Johan,

We did not yet port/test jBPM on the JBoss 4.0.4 branch, so there are probably some incompatibilities between jars. Are you sure you use the same jars for jBPM as for your JBoss instance?

Regards,
Koen

[j.hedin]

The only jars added to JBoss for jBPM are jbmp-3.1.jar and jbpm-3.1-identity.jar. Hibernate is read from JBoss 4.0.4.CR2 built in jar. JBPM works find with JMS, but having SLSB -> token.signal() -> SLSB gives the error. Will it help to rebuild jBPM from the source?

[koen.aers]

I suspect that is the problem yes... but I am not sure of course.

Regards,
Koen

[j.hedin]

I have checked the .jars. They only contains org.jbpm classes. Will a rebuild help then?

Should I have a reference to the EJB Hibernate Session factory for the jbpm-context?

 <jbpm-context>
 <service name="persistence">
 <factory>
 <bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory">
 <field name="isTransactionEnabled">
 <boolean value="false"/>
 </field>
 </bean>
 </factory>
 </service>

 <service name="message" factory="org.jbpm.msg.db.DbMessageServiceFactory"/>
 <service name="scheduler" factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory"/>
 <service name="logging" factory="org.jbpm.logging.db.DbLoggingServiceFactory"/>
 <service name="authentication" factory="org.jbpm.security.authentication.DefaultAuthenticationServiceFactory"/>
 </jbpm-context>

[koen.aers]

A rebuild will probably help. The problem is that there might be binary incompatibilities with the libraries of the JBoss AS 4.0.4 branch.

Regards,
Koen

[j.hedin]

Found it! jBPM worked all the time.

The second SLSB did throw a org.hibernate.HibernateException. Since that did mark the transaction for rollback org.jbpm.graph.def.Node.exceptionHandlers could not be executed and gave the org.jbpm.graph.def.DelegationException exception caused by the terminated Hibernate session instead of the exception thrown by the SLSB.

Not a bug, but a would suggest an enhancement to jBPM that shows the original exception as well in case that org.jbpm.graph.def.Node.exceptionHandlers could no be run.

Thanks for the quick help and keep up the good work!

Best regards
Johan Hedin