JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-533  -  IllegalStateException in driver in multi-server topology
Posted May 12, 2018 - updated Jun 01, 2018
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
    lolo4j
  • 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
    Normal
  • Reproducability
    Rarely
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.0
Issue description
In the dirver logs of a failed test of load-balancer state persistence in multi-server, I see the following stack trace: 
2018-05-12 20:10:59,727 [DEBUG][JPPF-0001           ][org.jppf.server.job.JPPFJobManager.jobEnded(166)] jobId 'testPersistentAlgos-proportional' ended
2018-05-12 20:10:59,728 [DEBUG][JobManager-0001     ][org.jppf.server.job.management.DriverJobManagement.sendNotification(223)] sending event JOB_ENDED for job JobInformation[jobUuid=98768233-45EB-071D-6C66-5BAA431E33A6, jobName=testPersistentAlgos-proportional, taskCount=0, initialTaskCount=100, priority=0, suspended=false, pending=false, maxNodes=2147483647], node=null
2018-05-12 20:10:59,735 [DEBUG][JPPF-0001           ][org.jppf.server.job.JPPFJobManager.jobQueued(145)] jobId 'testPersistentAlgos-proportional' queued
2018-05-12 20:10:59,736 [DEBUG][JobManager-0001     ][org.jppf.server.job.management.DriverJobManagement.sendNotification(223)] sending event JOB_QUEUED for job JobInformation[jobUuid=98768233-45EB-071D-6C66-5BAA431E33A6, jobName=testPersistentAlgos-proportional, taskCount=0, initialTaskCount=100, priority=0, suspended=false, pending=false, maxNodes=2147483647], node=null
2018-05-12 20:10:59,737 [DEBUG][JPPF-0002           ][org.jppf.nio.StateTransitionTask.run(90)] error on channel SelectionKeyWrapper[id=10, channel=java.nio.channels.SocketChannel[connected local=/127.0.0.1:11102 remote=/127.0.0.1:56375], readyOps=1, interestOps=0, context=ClientContext[channel=SelectionKeyWrapper[id=10], state=WAITING_JOB, uuid=B9700023-8320-CE2A-FACA-B38D9EF05B0E, connectionUuid=B9700023-8320-CE2A-FACA-B38D9EF05B0E_2, peer=false, ssl=false], nbTasksToSend=31, completedBundles={[]}] :
java.lang.IllegalStateException: Job ENDED
  at org.jppf.server.protocol.AbstractServerJobBase.addBundle(AbstractServerJobBase.java:235)
  at org.jppf.server.queue.JPPFPriorityQueue.addBundle(JPPFPriorityQueue.java:128)
  at org.jppf.server.nio.client.WaitingJobState.performTransition(WaitingJobState.java:87)
  at org.jppf.server.nio.client.WaitingJobState.performTransition(WaitingJobState.java:34)
  at org.jppf.nio.StateTransitionTask.run(StateTransitionTask.java:80)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
  at java.lang.Thread.run(Thread.java:745)
 Full logs provided in attached file

As a consequence, not all tasks results are sent back to the client
Steps to reproduce this issue
run the test test.org.jppf.load.balancer.persistence.TestMultiServerDatabaseLoadBalancerPersistence.testPersistentAlgos() until rerpoducing


#2
Comment posted by
lolo4j
May 12, 21:10
A file was uploaded. Logs of failed testicon_open_new.png
#4
Comment posted by
lolo4j
May 24, 07:05
Fixed in trunk/master

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Closed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from lolo4j to Not being worked on.
#5
Comment posted by
lolo4j
May 30, 08:41
This bug is not fixed smileys/4.png I can still reproduce it with the junit tests

The issue was updated with the following change(s):
  • The status has been updated, from Closed to New.
  • This issue has been reopened
  • The resolution has been updated, from RESOLVED to Not determined.