![]() Please wait while updating issue type...
Could not save your changes
This issue has been changed since you started editing it
Data that has been changed is highlighted in red below. Undo your changes to see the updated information
You have changed this issue, but haven't saved your changes yet. To save it, press the Save changes button to the right
This issue is blocking the next release
![]() There are no comments
There is nothing attached to this issue
This issue has no duplicates
There are no code checkins for this issue |
|||||||||||||||||||||||||||||||||||||
Really delete this comment?
Really delete this comment?
Complete driver thread dump showing deadlock.
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Number of threads on the driver may be the limiting factor, and my testing shows that number of connected nodes (and relative task completion rate), combined with heavy CPU load on the driver machine, may be the main contributors to that, rather than queue length itself.
Your fix appears to fix the deadlock, but there is now a NPE in either getAllJobIds() or getJobName(jobUUID), which I emailed you about separately.
Really delete this comment?
I found the problem, due to my fix in JPPFJobManager. I have now "fixed the fix" and uploaded the jars at the same location as the previous version.
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?