JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-98  -  Server discovery threads are duplicated int he client
Posted Nov 20, 2012 - updated Nov 24, 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
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Client
  • Resolution
    RESOLVED
  • Priority
    Low
  • Reproducability
    Always
  • Severity
    Low
  • Targetted for
    icon_milestones.png JPPF 3.2
Issue description
In the client, I noticed that the threads used to listen for driver connection information from a UDP multicast address on each interface are duplicated.

For instance, using VisualVM to inspect the threads of a client JVM, we can see the following in the threads inspector view: 
Receiver@192.168.1.14:11111
Receiver@192.168.1.14:11111
 example stack for these threads: 
"Receiver@192.168.1.14:11111" - Thread t@13
   java.lang.Thread.State: RUNNABLE
  at java.net.TwoStacksPlainDatagramSocketImpl.receive0(Native Method)
  - locked <6a4475e3> (a java.net.TwoStacksPlainDatagramSocketImpl)
  at java.net.TwoStacksPlainDatagramSocketImpl.receive(TwoStacksPlainDatagramSocketImpl.java:90)
  - locked <6a4475e3> (a java.net.TwoStacksPlainDatagramSocketImpl)
  at java.net.DatagramSocket.receive(DatagramSocket.java:786)
  - locked <3497c096> (a java.net.DatagramPacket)
  - locked <56e4d2d3> (a java.net.MulticastSocket)
  at org.jppf.comm.discovery.JPPFMulticastReceiver$Receiver.run(JPPFMulticastReceiver.java:252)
 
   Locked ownable synchronizers:
  - None

The attached screenshot clearly shows this is happening for each IP address (including IPv6) / network interface we listen to.
Steps to reproduce this issue
Start a client with server discovery enabled.

#2
Comment posted by
lolo4j
Nov 20, 05:26
A file was uploaded.
Screenshot illustrating the issue
Screenshot illustrating the issueicon_open_new.png
#4
Comment posted by
lolo4j
Nov 24, 18:40
Fixed in trunk revision 2551

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.