We're using OFBiz version 3.2. But i took a look at the current trunk, if t´something happens regarding this but i my thought the code still behaves the same.
jacques.le.roux wrote: > > Which version are you using ? > > Jacques > > From: "maburger" <[EMAIL PROTECTED]> >> >> 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. >> > > -- View this message in context: http://www.nabble.com/Problem-with-queued-job-after-after-execution-error.-tp18961750p18975579.html Sent from the OFBiz - User mailing list archive at Nabble.com.
