Hide Forgot
Date of First Response: 2008-11-20 22:15:15 project_key: SOA Due to changes in transaction lookup in jBPM 3.2.3 it is necessary to set jta.UserTransaction property in hiberante.cfg.xml to UserTransaction. Also this must be documented in Release Notes in case of upgrading older installations.
Link: Added: This issue is related to JBPM-1179
Link: Added: This issue is a dependency of SOA-796
The change in transaction lookup is now also present on the 3.2.2 SOA branch of the jBPM code. Thus, we must set the "jta.UserTransaction" property for SOA 4.2.0 CP03.
Link: Added: This issue is related to SOA-959
Fixed in revision 2333 of: build-tools/builders/jbpm/build.xml Commit message: Add: <property name="jta.UserTransaction">UserTransaction</property> to the "JTA transaction properties" section of the hibernate.cfg.xml file in jbpm.esb. Fixes JIRA SOA-1039. This change needs to be documented in the release notes (.e.g.): Upgrading from an earlier 4.2.0 release of the JBoss Enterprise SOA Platform The fix for issue SOA-1039 (JBPM-1179) requires that the property: <property name="jta.UserTransaction">UserTransaction</property> is added to the file: <serverroot>/jboss-as/server/<config>/deploy/jbpm.esb/hibernate.cfg.xml in order to maintain backward compatibility with earlier releases. This change is already present in the file as shipped with the 4.2.0 CP03 release but must be added if configuration files are manually upgraded.
Known issue added: Hibernate UserTransaction property requirement As of release 4.2.CP03, it is now necessary to set the jta.UserTransaction property in hibernate.cfg.xml to UserTransaction. This is due to changes required in transaction lookup in jBPM 3.2.3. Additional information: http://jira.jboss.com/jira/browse/JBPM-1179
added to release notes
The jta.UserTransaction property was added to the hibernate.cfg.xml files included in the SOA-P servers for 4.2 CP03 CR5 and it was included in some of the examples, but not all. We can cover that in documentation. One question - the property was not added to: ./jboss-soa-p.4.2.0/jbpm-jpdl/config/hibernate.cfg.xml ./jboss-soa-p-standalone.4.2.0/jbpm-jpdl/config/hibernate.cfg.xml Will this be a functional issue for users? Will we ship a standalone version of jBPM at the same time as 4.2 CP03? ./jboss-soa-p.4.2.0/jbpm-jpdl/config/hibernate.cfg.xml ./jboss-soa-p.4.2.0/jbpm-jpdl/examples/rulesAssignmentHandler/src/config/hibernate.cfg.xml ./jboss-soa-p.4.2.0/jbpm-jpdl/examples/rulesActionHandler/src/config/hibernate.cfg.xml ./jboss-soa-p.4.2.0/jbpm-jpdl/examples/customTaskInstance/src/main/config/hibernate.cfg.xml ./jboss-soa-p.4.2.0/seam/examples/dvdstore/resources/hibernate.cfg.xml ./jboss-soa-p.4.2.0/seam/examples/hibernate2/resources/websphere/hibernate.cfg.xml ./jboss-soa-p.4.2.0/seam/examples/hibernate2/resources/hibernate.cfg.xml ./jboss-soa-p.4.2.0/seam/examples/hibernate2/resources/weblogic/hibernate.cfg.xml ./jboss-soa-p.4.2.0/seam/examples/hibernate2/resources/glassfish/hibernate.cfg.xml ./jboss-soa-p.4.2.0/seam/examples/hibernate/resources/hibernate.cfg.xml ./jboss-soa-p.4.2.0/seam/examples/portal/resources/hibernate.cfg.xml ./jboss-soa-p.4.2.0/seam/examples/todo/resources/hibernate.cfg.xml ./jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/helloworld_hibernate_action/hibernate.cfg.xml ./jboss-soa-p.4.2.0/jboss-as/server/production/deploy/jbpm.esb/hibernate.cfg.xml ./jboss-soa-p.4.2.0/jboss-as/server/all/deploy/jbpm.esb/hibernate.cfg.xml ./jboss-soa-p-standalone.4.2.0/jbpm-jpdl/config/hibernate.cfg.xml ./jboss-soa-p-standalone.4.2.0/jbpm-jpdl/examples/rulesAssignmentHandler/src/config/hibernate.cfg.xml ./jboss-soa-p-standalone.4.2.0/jbpm-jpdl/examples/rulesActionHandler/src/config/hibernate.cfg.xml ./jboss-soa-p-standalone.4.2.0/jbpm-jpdl/examples/customTaskInstance/src/main/config/hibernate.cfg.xml ./jboss-soa-p-standalone.4.2.0/jboss-as/samples/quickstarts/helloworld_hibernate_action/hibernate.cfg.xml ./jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbpm.esb/hibernate.cfg.xml [ldimaggi@ldimaggi 42_CP03_CR5]$ files=$( find . -name hibernate.cfg.xml ) [ldimaggi@ldimaggi 42_CP03_CR5]$ grep "jta.UserTransaction" $files ./jboss-soa-p.4.2.0/jbpm-jpdl/examples/rulesAssignmentHandler/src/config/hibernate.cfg.xml: <property name="jta.UserTransaction">java:comp/UserTransaction</property> ./jboss-soa-p.4.2.0/jbpm-jpdl/examples/rulesActionHandler/src/config/hibernate.cfg.xml: <property name="jta.UserTransaction">java:comp/UserTransaction</property> ./jboss-soa-p.4.2.0/jbpm-jpdl/examples/customTaskInstance/src/main/config/hibernate.cfg.xml: <property name="jta.UserTransaction">java:comp/UserTransaction</property> ./jboss-soa-p.4.2.0/jboss-as/server/production/deploy/jbpm.esb/hibernate.cfg.xml: <property name="jta.UserTransaction">UserTransaction</property> ./jboss-soa-p.4.2.0/jboss-as/server/all/deploy/jbpm.esb/hibernate.cfg.xml: <property name="jta.UserTransaction">UserTransaction</property> ./jboss-soa-p-standalone.4.2.0/jbpm-jpdl/examples/rulesAssignmentHandler/src/config/hibernate.cfg.xml: <property name="jta.UserTransaction">java:comp/UserTransaction</property> ./jboss-soa-p-standalone.4.2.0/jbpm-jpdl/examples/rulesActionHandler/src/config/hibernate.cfg.xml: <property name="jta.UserTransaction">java:comp/UserTransaction</property> ./jboss-soa-p-standalone.4.2.0/jbpm-jpdl/examples/customTaskInstance/src/main/config/hibernate.cfg.xml: <property name="jta.UserTransaction">java:comp/UserTransaction</property> ./jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbpm.esb/hibernate.cfg.xml: <property name="jta.UserTransaction">UserTransaction</property>
The jta.UserTransaction property is now added to the standalone jBPM build: build-tools/builders/jbpm/build.xml Revisions 2454 4.2.0 branch 2455 4.3 branch 2456 trunk Commit message: Also add a jta.UserTransaction property to the "standalone" jbpm-jpdl build.
Verified in CR5