Hi Stefan,
Thanks, that was helpful already.
Regards,
Konrad
> On 3. Apr 2024, at 10:40, Stefan Egli <[email protected]> wrote:
>
> Hi Konrad,
>
> Suspend stops processing of new jobs but finishes already started jobs (note
> that the default implementation suspends for 60min, then resumes the queue).
> This has no influence on enqueuing, so jobs can still be enqueued.
>
> I'm not aware of any helper that goes through the stack trace to find which
> code added a job. There is (debug) logging though, so that might be of some
> help.
>
> Cheers,
> Stefan
>
> On 02.04.24 18:04, Konrad Windszus wrote:
>> Hi
>> I currently face an issue with jobs which get constantly queued (unclear by
>> whom yet).
>> In order to bring back back the server to a stable state I want to leverage
>> the web console at /system/console/slingevent which offers 4 actions per
>> each active job queue:
>>
>> Reset Stats
>> Resume/Suspend
>> Test
>> Drop Alll
>>
>> (https://github.com/apache/sling-org-apache-sling-event/blob/71c6d4b3219adb640fa5628fb31cad84d31eff2b/src/main/java/org/apache/sling/event/impl/jobs/console/WebConsolePlugin.java#L297-L304)
>>
>> What happens exactly if I suspend a queue? Do jobs still get enqueued on the
>> suspended queue? Is there any helper available to figure out which code is
>> responsible for adding jobs?
>> Thanks in advance
>>
>> Konrad
>>
>>
>>
>>
>>
