[
http://jira.jboss.com/jira/browse/JBPM-1135?page=comments#action_12419917 ]
Peter Brewer commented on JBPM-1135:
------------------------------------
Looking at the stack I decided to modify my test process to demonstrate the issue. The
issue occurs when a timer fires and then in the same execution another timer is created.
This can be observed using the attached process definition file (timerTest2.xml)
JobSession.deleteJobsForProcessInstance doesn't work if jbpm
isn't the transaction manager
------------------------------------------------------------------------------------------
Key: JBPM-1135
URL:
http://jira.jboss.com/jira/browse/JBPM-1135
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jPDL 3.2.2
Reporter: Jérôme Tellier
Assigned To: Alejandro Guizar
Attachments: processdefinition.xml
My configuration of the persistence service is this :
<service name="persistence">
<factory>
<bean
class="org.jbpm.persistence.db.DbPersistenceServiceFactory">
<field name="isCurrentSessionEnabled"><false
/></field>
<field name="isTransactionEnabled"><false
/></field>
</bean>
</factory>
</service>
When I call JobSession.deleteJobsForProcessInstance, the method beforeCompletion() in
DeleteJobsSynchronization is never call in the commit, probably because jbpm isn't the
transaction manager.
--
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