JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-81  -  FAIL: TestExecutorServiceConfiguration.testSubmitWithClientExecutionPolicy
Posted Oct 16, 2012 - updated Oct 17, 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
    jandam
  • Owned by
    Not owned by anyone
  • Category
    Client
  • Resolution
    RESOLVED
  • Priority
    High
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.2
Issue description
On slow single core Win XP machine test TestExecutorServiceConfiguration.testSubmitWithClientExecutionPolicy failed on timeout. The test submits 10 tasks to JPPFExecutorService for local execution on client. Tasks count in JPPFJob: 1-2-2-2-2-1. Last JPPFJob with one task is not submitted to JPPFClient. BatchHandler thread is waiting on submittingJob.await() in BatchHandler.updateNextJob(false).
Steps to reproduce this issue
run TestExecutorServiceConfiguration.testSubmitWithClientExecutionPolicy


#2
Comment posted by
jandam
Oct 16, 16:15
A file was uploaded. Console output with debug informationicon_open_new.png
#3
Comment posted by
jandam
Oct 16, 16:16
A file was uploaded. ThreadDumpicon_open_new.png
#4
Comment posted by
lolo4j
Oct 17, 06:18
I oculd not reproduce on my side but I think I found where the rpoblem is.

I committed a fix in revision 2478.
#6
Comment posted by
lolo4j
Oct 17, 07:01
Actually, I found a way for my VirtualBox VM to use only half a physical processor, and I could reproduce with that configuration. I also confirm that the fix is working.

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.