JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-113  -  NullPointerException in the console upon connection to first driver
Posted Jan 05, 2013 - updated Jan 05, 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
    GUI
  • Resolution
    RESOLVED
  • Priority
    High
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.3
Issue description
When the administration console is configured with "jppf.discovery.enabled = false", I get the following exception in the GUI's console output:

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
  at org.jppf.ui.monitoring.data.StatsHandler$1.run(StatsHandler.java:434)
  at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
  at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:701)
  at java.awt.EventQueue.access$000(EventQueue.java:102)
  at java.awt.EventQueue$3.run(EventQueue.java:662)
  at java.awt.EventQueue$3.run(EventQueue.java:660)
  at java.security.AccessController.doPrivileged(Native Method)
  at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
  at java.awt.EventQueue.dispatchEvent(EventQueue.java:671)
  at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:244)
  at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:163)
  at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
  at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:147)
  at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:139)
  at java.awt.EventDispatchThread.run(EventDispatchThread.java:97)
The following is also printed in the GUI's log file:
2013-01-05 05:44:22,216 [ERROR][org.jppf.client.JPPFClientConnectionImpl.init(122)]: 
java.lang.NullPointerException
  at org.jppf.ui.monitoring.node.NodeDataPanelManager.findDriver(NodeDataPanelManager.java:249)
  at org.jppf.ui.monitoring.node.ConnectionStatusListener.statusChanged(ConnectionStatusListener.java:73)
  at org.jppf.client.AbstractJPPFClientConnection.fireStatusChanged(AbstractJPPFClientConnection.java:219)
  at org.jppf.client.AbstractJPPFClientConnection.setStatus(AbstractJPPFClientConnection.java:173)
  at org.jppf.client.AbstractJPPFClientConnection.processStatusChanged(AbstractJPPFClientConnection.java:311)
  at org.jppf.client.AbstractJPPFClientConnection.taskServerConnectionStatusChanged(AbstractJPPFClientConnection.java:297)
  at org.jppf.client.JPPFClientConnectionImpl$2.statusChanged(JPPFClientConnectionImpl.java:107)
  at org.jppf.client.AbstractClientConnectionHandler.fireStatusChanged(AbstractClientConnectionHandler.java:172)
  at org.jppf.client.AbstractClientConnectionHandler.setStatus(AbstractClientConnectionHandler.java:122)
  at org.jppf.client.TaskServerConnectionHandler.init(TaskServerConnectionHandler.java:97)
  at org.jppf.client.JPPFClientConnectionImpl.connect(JPPFClientConnectionImpl.java:144)
  at org.jppf.client.JPPFClientConnectionImpl.init(JPPFClientConnectionImpl.java:110)
  at org.jppf.client.ConnectionInitializer.run(ConnectionInitializer.java:58)
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
  at java.util.concurrent.FutureTask.run(FutureTask.java:166)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
  at java.lang.Thread.run(Thread.java:722)
This does not occur when discovery is enabled

Steps to reproduce this issue
  • configure the admin console with "jppf.discovery.enabled = false" and define a single driver connection
  • start a driver
  • start the administration console
==> you can see the NPEs as in the bug description

#4
Comment posted by
 lolo4j
Jan 05, 08:25
Fixed. Changes committed to SVN:

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Confirmed 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.