JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-380  -  Confusing IOException from the JMX connector upon closing a JPPFClient
Posted Apr 04, 2015 - updated Aug 15, 2018
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
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.0.x
Issue description
Sometimes, the JMXMP connector will throw the following exception when a JPPFClient is closed: 
java.io.IOException: The connection has been closed.
  at com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl.checkState(ClientSynchroMessageConnectionImpl.java:446)
  at com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl.sendWithReturn(ClientSynchroMessageConnectionImpl.java:206)
  at javax.management.remote.generic.ClientIntermediary$GenericClientNotifForwarder.fetchNotifs(ClientIntermediary.java:503)
  at com.sun.jmx.remote.opt.internal.ClientNotifForwarder$NotifFetcher.fetchNotifs(ClientNotifForwarder.java:354)
  at com.sun.jmx.remote.opt.internal.ClientNotifForwarder$NotifFetcher.run(ClientNotifForwarder.java:278)
  at java.lang.Thread.run(Thread.java:745)
 In fact, this exception is harmless and can be safely ignored, but it can be confusing to anyone not aware of it.
Steps to reproduce this issue
  • start a driver
  • start a client application which creates a JPPFClient, registers a notification listener on the driver's job management MBean then closes the client
==> you will see the IOException

#3
Comment posted by
lolo4j
Apr 19, 22:11
Fixed in: