topic Re: CommendContext Error handling? in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/commendcontext-error-handling/m-p/215096#M168226 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><BR /><SPAN>I think your point about the log level for the other exceptions is correct. We've changed it just now.</SPAN><BR /><SPAN>For Optimistic locking exceptions the log level is set to debug on purpose. The Engine will handle optimstic locking exceptions and the log message is mainly useful in debugging cases.</SPAN><BR /><BR /><SPAN>Best regards,</SPAN></BODY></HTML> Mon, 18 Jul 2016 10:34:17 GMT trademak 2016-07-18T10:34:17Z CommendContext Error handling? https://connect.hyland.com/t5/alfresco-archive/commendcontext-error-handling/m-p/215095#M168225 I understand from BpmnError catching that JavaDelegates should throw a BpmnError when catching an exception.But what if it's an uncaught exception (NullPointer, ClassCast, etc). Accidents can happen, after all.Presently CommandContext logs this as a DEBUG level… That's not ideal. Optimistic locking Thu, 07 Jul 2016 13:08:23 GMT https://connect.hyland.com/t5/alfresco-archive/commendcontext-error-handling/m-p/215095#M168225 jonnyg 2016-07-07T13:08:23Z Re: CommendContext Error handling? https://connect.hyland.com/t5/alfresco-archive/commendcontext-error-handling/m-p/215096#M168226 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><BR /><SPAN>I think your point about the log level for the other exceptions is correct. We've changed it just now.</SPAN><BR /><SPAN>For Optimistic locking exceptions the log level is set to debug on purpose. The Engine will handle optimstic locking exceptions and the log message is mainly useful in debugging cases.</SPAN><BR /><BR /><SPAN>Best regards,</SPAN></BODY></HTML> Mon, 18 Jul 2016 10:34:17 GMT https://connect.hyland.com/t5/alfresco-archive/commendcontext-error-handling/m-p/215096#M168226 trademak 2016-07-18T10:34:17Z