[
http://jira.jboss.com/jira/browse/JBPM-1135?page=comments#action_12420890 ]
Alejandro Guizar commented on JBPM-1135:
----------------------------------------
Locked timers associated with the ending process instance are excluded from deletion. If a
job is locked it is quite probably being executed already; deleting it will not stop its
execution. After it executes the job executor will delete it. Repeating timers are a
special case; timer.execute() checks whether the process instance has ended before
performing any action
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, timerTest2.log
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