JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
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
     
    		 Closed
  • Assigned to
    jandam
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Server
  • Resolution
    RESOLVED
  • Priority
    High
  • Reproducability
    Always
  • Severity
    Normal
  • 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(JPPFPriorityQueue.java:151)
  at org.jppf.server.nio.client.WaitingJobState.performTransition(WaitingJobState.java:78)
  at org.jppf.server.nio.client.WaitingJobState.performTransition(WaitingJobState.java:1)
  at org.jppf.server.nio.StateTransitionTask.run(StateTransitionTask.java:82)
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
  at java.util.concurrent.FutureTask.run(FutureTask.java:166)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
  at java.lang.Thread.run(Thread.java:722)
 Full driver and client logs can be found attached to this bug.
Steps to reproduce this issue
  • extract the attached code and config (sample.zip) : 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

#2
Comment posted by
lolo4j
Sep 23, 18:01
A file was uploaded. reproducing sample code and configurationicon_open_new.png
#3
Comment posted by
lolo4j
Sep 23, 18:02
A file was uploaded. client and server logs with related stack tracesicon_open_new.png
#5
Comment posted by
lolo4j
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.
#8
Comment posted by
jandam
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.