|
Am 05.08.2021 um 16:27 schrieb David Gibbs via JAVA400-L <java400-l@xxxxxxxxxxxxxxxxxx>:
Folks:
I'm looking for advice on the best way to detect if a job is actually doing work.
Currently I'm getting the call stack from the Job object and comparing various attributes of it to a previously retrieved call stack. Sadly, the CallStackEntry class doesn't implement a proper equals method.
If the current call stack is different from the previous call stack, I'm taking that as a hint that the job is doing work.
Are there any other job attributes, or techniques, you can think of that would be useful in identifying a hung vs. active job?
Thanks!
david
--
I'm riding in the American Diabetes Association's Tour de Cure to raise money for diabetes research, education, advocacy, and awareness. You can make a tax-deductible donation to my ride by visiting https://mideml.diabetessucks.net.
You can see where my donations come from by visiting my interactive donation map ... https://mideml.diabetessucks.net/map (it's a geeky thing).
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/java400-l.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.