[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2694) JTA Transaction - couldn't lookup 'UserTransaction' from jndi
[
https://jira.jboss.org/jira/browse/JBPM-2694?page=com.atlassian.jira.plug...
]
Martin Porter commented on JBPM-2694:
-------------------------------------
Hi,
I have made the appropriate change in the JtaTransaction class and created a new
Command<> class to read the config from Hibernate. It has been tested on WLS 11g and
it works (10.3.2.0) so it needs to be tested on JBoss. It will use the values found in the
hibernate config so these of course must be correct and present. These values are:-
hibernate.transaction.manager_lookup_class
jta.UserTransaction
If either of these is not found then it will default to the JBoss value. So BOTH must be
specified or neither specified for this to work correctly.
Regards
Martin
JTA Transaction - couldn't lookup 'UserTransaction' from
jndi
-------------------------------------------------------------
Key: JBPM-2694
URL: https://jira.jboss.org/jira/browse/JBPM-2694
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.2, jBPM 4.1, jBPM 4.0
Environment: Application Server Oracle Weblogic 10.3
Java 6
DB2 v9
Windows XP Professional
Reporter: P. De Bock
On Oracle Weblogic 10.3, the JTA transaction feature causes an exception.
org.jbpm.api.JbpmException: couldn't lookup 'UserTransaction' from jndi:
Unable to resolve 'UserTransaction'. Resolved '': Unable to resolve
'UserTran
saction'. Resolved ''
at
org.jbpm.pvm.internal.tx.jta.JtaTransaction.lookupFromJndi(JtaTransaction.java:137)
at
org.jbpm.pvm.internal.tx.jta.JtaTransaction.lookupJeeUserTransaction(JtaTransaction.java:116)
at
org.jbpm.pvm.internal.tx.jta.JtaRetryInterceptor.execute(JtaRetryInterceptor.java:42)
at
org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
at
org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.jbpm.pvm.internal.svc.SkipInterceptor.execute(SkipInterceptor.java:43)
at
org.jbpm.pvm.internal.cfg.ProcessEngineImpl.checkDb(ProcessEngineImpl.java:177)
at
org.jbpm.pvm.internal.cfg.ProcessEngineImpl.buildProcessEngine(ProcessEngineImpl.java:170)
...
Default Weblogic JNDI reference = 'javax.transaction.UserTransaction' but jBPM
4.2 only support standard JEE specs ('UserTransaction').
With, jBPM 3.3, it's possible to override the jndi name value as a property in the
jbpm hibernate config file (<property
name="jta.UserTransaction">java:comp/UserTransaction</property>).
Ref : http://docs.jboss.org/jbpm/v3/userguide/deployment.html
I am not sure that jBPM 4.2 implements that solution.
I also know that "JTA Transactions" is in Incubation and is not documented in
Developers Guide and that app-servers ohter than jBOSS are not assumed to be supported.
Does a actual solution or work-around exist for that problem with released 4.2 version ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira