JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-70  -  IllegalStateException: Job xxx already enqueued when job is submitted via multiple channels
Posted Sep 23, 2012 - updated Oct 18, 2012
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
  • Assigned to
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
  • Resolution
  • Priority
  • Reproducability
  • Severity
  • Targetted for
    icon_milestones.png JPPF 3.2
Issue description
When a job is submmitted via multiple channels, I can see the following stack trace in the driver's log:
java.lang.IllegalStateException: Job job-1 already enqueued
  at org.jppf.server.queue.JPPFPriorityQueue.addBundle(
  at org.jppf.server.nio.client.WaitingJobState.performTransition(
  at org.jppf.server.nio.client.WaitingJobState.performTransition(
  at java.util.concurrent.Executors$
  at java.util.concurrent.FutureTask$Sync.innerRun(
  at java.util.concurrent.ThreadPoolExecutor.runWorker(
  at java.util.concurrent.ThreadPoolExecutor$
Full driver and client logs can be found attached to this bug.
Steps to reproduce this issue
  • extract the attached code and config ( : runner + task + 1 driver with local node + 1 clinet with 2 channels to the server
  • run the sample code with the attached config
  • ==> you will see in the client console that one fo the channels disconnects then reconnects at least one
  • ==> you will see the stack trace above int he resulting driver log

Comment posted by
Sep 23, 18:01
A file was uploaded. reproducing sample code and configurationicon_open_new.png
Comment posted by
Sep 23, 18:02
A file was uploaded. client and server logs with related stack tracesicon_open_new.png
Comment posted by
Sep 23, 18:12
Woraround: currently to work around this issue, one can use JPPFJob.getClientSLA().setMaxNodes(1) to limit the number of channels to 1, or set an appropriate client-side execution policy so the problem doesn't occur.
Comment posted by
Oct 18, 11:24
Fixed by commit in trunk revision 2482

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Being worked on to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from jandam to Not being worked on.