JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-41  -  BarChart: queue size sometimes negative
Posted Aug 08, 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
    lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Time spent
    1 week, 4 days, 2 hours
  • Category
    Management / Monitoring
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Low
  • Targetted for
    icon_milestones.png JPPF 3.2
Issue description
During task execution sometimes Queue Size Bar chart in admin tool shows negative value.

Steps to reproduce this issue
2 nodes, ~6000 tasks, 50 tasks/job, balancing: fixed=1

#2
Comment posted by
lolo4j
Aug 08, 23:39
2xJOB_ENDED when exception in broadcast job 
[java] java.lang.Throwable: JobEventTask: JOB_ENDED on null
[java] at org.jppf.server.job.JobEventTask.<init>(JobEventTask.java:69)
[java] at org.jppf.server.job.JPPFJobManager.submitEvent(JPPFJobManager.java:206)
[java] at org.jppf.server.job.JPPFJobManager.jobEnded(JPPFJobManager.java:171)
[java] at org.jppf.server.queue.BroadcastJobCompletionListener.taskCompleted(BroadcastJobCompletionListener.java:91)
[java] at org.jppf.server.protocol.JPPFTaskBundle.fireTaskCompleted(JPPFTaskBundle.java:301)
[java] at org.jppf.server.nio.nodeserver.WaitingResultsState.performTransition(WaitingResultsState.java:104)
[java] at org.jppf.server.nio.nodeserver.WaitingResultsState.performTransition(WaitingResultsState.java:33)
[java] at org.jppf.server.nio.StateTransitionTask.run(StateTransitionTask.java:85)
[java] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[java] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
[java] at java.util.concurrent.FutureTask.run(FutureTask.java:166)
[java] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[java] at java.lang.Thread.run(Thread.java:722)
[java] java.lang.Throwable: JobEventTask: JOB_ENDED on null
[java] at org.jppf.server.job.JobEventTask.<init>(JobEventTask.java:69)
[java] at org.jppf.server.job.JPPFJobManager.submitEvent(JPPFJobManager.java:206)
[java] at org.jppf.server.job.JPPFJobManager.jobEnded(JPPFJobManager.java:171)
[java] at org.jppf.server.nio.client.ClientContext.jobEnded(ClientContext.java:323)
[java] at org.jppf.server.nio.client.SendingResultsState.performTransition(SendingResultsState.java:90)
[java] at org.jppf.server.nio.client.SendingResultsState.performTransition(SendingResultsState.java:33)
[java] at org.jppf.server.nio.StateTransitionTask.run(StateTransitionTask.java:85)
[java] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[java] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
[java] at java.util.concurrent.FutureTask.run(FutureTask.java:166)
[java] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)

Problem is with broadcast job. BroadcastJobCompletionListener fires jobEnded when broadcast job has all tasks completed. But ClientContext.jobEnded is notified too (same for standard job)

Queue Size after 1st execution is 0, second = -2, and third execution = -4.

#5
Comment posted by
jandam
Oct 18, 11:21
Fixed in trunk revision 2482

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New 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 lolo4j to Not being worked on.
  • Time spent on this issue, from No time spent to 1 week, 4 days, 2 hours.