[
https://jira.jboss.org/browse/JBPM-2879?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2879:
-----------------------------------
Fix Version/s: (was: jBPM 4.4)
Resolutions other than "done" should not have a fix version set.
lookupJeeTransactionManager() method in
org.jbpm.pvm.internal.tx.JtaTransaction class has problem if used in Tomcat with JOTM
-----------------------------------------------------------------------------------------------------------------------------
Key: JBPM-2879
URL:
https://jira.jboss.org/browse/JBPM-2879
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: jBPM4.3, apache-tomcat-6.0.14, jdk1.6.0_11, MySQL
Reporter: Jayanta Sarkar
Assignee: Huisheng Xu
Priority: Critical
The lookupJeeTransactionManager() method in org.jbpm.pvm.internal.tx.JtaTransaction class
cannot obtain TransactionManager through JNDI look up in Tomcat with JOTM. The reason is
there is no separate TransactionManager implementation in JOTM. The class which provides
the implementation for UserTransaction is org.objectweb.jotm.Current.java internally
implements javax.transaction.TransactionManager. So if we add some code in the
lookupJeeTransactionManager() method as below this works:
if (transactionManager == null)
{
UserTransaction ut = (UserTransaction) lookupFromJndi(userTransactionJndiName);
if (ut instanceof TransactionManager)
{
System.out.println("lookupJeeTransaction:: found TransactionManager");
transactionManager = ((TransactionManager) ut);
}
}
We need to modify this code such a way so that it works in all server with all JTA
implementation. I am in the process of making some patch for this and will send that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira