JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-102  -  Ongoing issues with the administration and monitoring console
Posted Dec 10, 2012 - updated Mar 22, 2013
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
    Management / Monitoring
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Often
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.3
Issue description
This is to keep track of small, but annoying, issues in the console. Here's what I notcied so far:
  • latest number of jobs is sometimes negative
  • in the "job data" view, some jobs are not "cleaned up" and are still displayed even though they completed some time ago. As a workaround, clicking on the "Refresh" button restores a proper display
  • in the "job data" view, the current number of tasks being executed n the nodes for a given job is incorrect: often 0, sometimes negative (especially when using a topology with multiple connected drivers)
  • the "latest job execution time" field is missing in the charts configuration view and in the server statistics "Jobs" section
  • the number of tasks executed for each node should be formatted using grouping according to the current locale
Steps to reproduce this issue
Run a JPPF test witht he admin conosle started.

#6
Comment posted by
 lolo4j
Dec 15, 18:04
Fixed the last 3 bullet points: number of node job tasks in job data view, added "latest job execution time", number of tasks executed by a node is now formatted in topology view.. Committed to SVN trunk revision 2569
#8
Comment posted by
 lolo4j
Mar 22, 21:00
Fixed the remaining issues: trunk revision 2661

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.