Hi *, we have a problem with the service engine. In our scenario a job has been queued (JOB_SANDBOX entry is set to SERVICE_RUNNING) and the job throws an unexpected exception (no InvalidJobException) within the GenericServiceJob.init() method (this is called within the GenericServiceJob.exec() method). This exception is not handled by the engine (the calling JobInvoker only handles InvalidJobExceptions), so the job "hangs" within the SERVICE_RUNNING status. Wouldn't it be correct to reset the status to crashed or pending for example? This causes the job not to be rescheduled.
Best regards M. B. -- View this message in context: http://www.nabble.com/Problem-with-queued-job-after-after-execution-error.-tp18961750p18961750.html Sent from the OFBiz - User mailing list archive at Nabble.com.
