JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-290  -  New connected nodes are not automatically enrolled in notification forwarding
Posted Jul 02, 2014 - updated Mar 28, 2016
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
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.1.x
Issue description
When a node is restarted, the notifications sent by its MBeans are no longer forwarded to notification listeners registered with the server to which it is attached.
Steps to reproduce this issue
  • start a driver and a node
  • from a client application, register a forwarding listener (for JPPFNodeForwardingMBean and the ALL_NODES selector) which prints out the notifications it receives
  • submit a job with a single task which sends a notification ==> the notification is displayed
  • from the same client, restart the node, then submit a second job with a similar task
  • ==> the second job completes properly, but no notification is displayed

#3
Comment posted by
lolo4j
Jul 04, 08:17
fixed in:
#5
Comment posted by
lolo4j
Jul 05, 09:47
The fix was causing the server to not submit jobs to offline nodes. This is corrected in: