[ https://jira.jboss.org/jira/browse/JBPM-2488?page=com.atlassian.jira.plug... ] Julian Coleman updated JBPM-2488: --------------------------------- Affects Version/s: jBPM 3.2.x Affected version is 3.2.7 CR1/jbpm-3.2-soa branch. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2488?page=com.atlassian.jira.plug... ] Alejandro Guizar commented on JBPM-2488: ---------------------------------------- Another option would be to switch to an essentially unlimited character type. This was done for Sybase a while back: JBPM-2057. To avoid further schema changes in other databases I am going to take the path that Ronald suggests, pending further discussion on the consequences of trimming. In particular, the innermost exception, the bottom of the exception chain, is the one that provides the most precise information. If we trim the stack trace, it is possible the most valuable information is lost. This is why JBPM-2057 was resolved by switching to text instead. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2488?page=com.atlassian.jira.plug... ] Alejandro Guizar reassigned JBPM-2488: -------------------------------------- Assignee: Alejandro Guizar -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2488?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-2488: ----------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes The statement "all jobs in job executor are processed in the same transaction" is inaccurate. Each job is processed in a separate transaction. Process execution gets blocked because job executor threads do not ever give up on a job if the exception is related to persistence. No SQLException ever reaches the job executor. It is always wrapped in a HibernateException. Not retrying after one such exception would unnecessarily affect the availability of the affected process. The error condition could be simply a locking issue (e.g. StaleStateException, LockAcquisitionException) or a temporary condition (database host unreachable). Other issues (e.g. the one at hand) can be arguably considered as bugs, either in jBPM classes or in user code. -- 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