[
http://jira.jboss.com/jira/browse/JBPM-877?page=comments#action_12355181 ]
David Lloyd commented on JBPM-877:
----------------------------------
This brought up a serious problem - jbpmContext.setRollbackOnly() did not cause the
transaction to roll back! This is very serious because many operations in the web console
are compound operations, and transactions are used to ensure that the database is never
left in an inconsistent state.
jta configuration for process deployment in enterprise environment
------------------------------------------------------------------
Key: JBPM-877
URL:
http://jira.jboss.com/jira/browse/JBPM-877
Project: JBoss jBPM
Issue Type: Task
Components: Core Engine
Reporter: Tom Baeyens
Assigned To: David Lloyd
Fix For: jBPM jPDL 3.2
another bug report from Jeff:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019684#...
"
I have reported this before:
21:11:35,953 ERROR [[ProcessUploadServlet]] Servlet.service() for servlet Proces
sUploadServlet threw exception
org.hibernate.HibernateException: Unable to locate current JTA transaction
at org.hibernate.context.JTASessionContext.currentSession(JTASessionCont
it requires changes to jbpm.cfg.xml
to set to false and CMTTransactionFactory to JTATransactionFactory
org.hibernate.transaction.JTATransactionFactory
"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira