Job Executor hangs or stops acquiring jobs? (solved: HTTP-Connector stuck in endless job due to long http request/no response)

[thorben]

@StephenOTT

Would this scenario not warrant a wrapper around a job so that infinite loops, waiting forever, etc cannot occur? So that even if a loop does occur as a job, the higher level abstraction will timeout.

If you have a concrete idea, please provide some code. I don’t know how to build such a thing in a good way.

Note that the job’s lock expiration time is already such a timeout. This ensures that the job will be triggered again, but it does not cancel the ongoing execution. So if you have an infinite loop in a JavaDelegate or similar, all the job executor’s threads will be busy after some time.