[
https://jira.jboss.org/jira/browse/JBPM-2691?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-2691:
----------------------------------------
Reverted command to save job exception. ESB message service will implement its own
behavior, cf. SOA-1882.
ExecuteJobCommand no longer attempts to save the exception or retry the job. These
responsibilities are fully delegated to the MDB container.
Save exceptions thrown while executing a job in a separate
transaction
----------------------------------------------------------------------
Key: JBPM-2691
URL:
https://jira.jboss.org/jira/browse/JBPM-2691
Project: jBPM
Issue Type: Bug
Affects Versions: jBPM 3.2.8
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.9
Attachments: JobExecutorThread.diff
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Currently the stack trace printout is saved in the same transaction provided the
exception is not related to persistence. This scheme has two drawbacks:
1. Exceptions not related to persistence may still leave the job and the process instance
as a whole in an inconsistent state.
2. Persistence exceptions are never saved.
Hence saving the stack trace in a separate transaction would be preferable.
--
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