JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-76  -  Make sure JPPF is IPv6-ready
Posted Oct 02, 2012 - updated Nov 01, 2012
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Enhancement
  • 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
    Networking
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.2
Issue description
Given the current global shortage of IPv4 addresses, it is likely that usage of IPv6 wil grow exponentially very soon.

We need to make sure that JPPF is ready for that. Areas to check:
  • discovery, including broadcasting and receiving UDP multicats packets, as well as IP filtering
  • connection to the servers from nodes, clients, peer servers, both plain and secure
  • JMX connections, plain and secure

#3
Comment posted by
lolo4j
Oct 18, 20:36
The only place I found in the code where IPv6-specific was needed was in the initialization of JMXConnectionWrapper, where the building of the JMXServiceURL takes place. When building the URL IPv6 addresses for the host need to be surrounded with square brackets.

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.
#5
Comment posted by
lolo4j
Oct 26, 08:00
I'm reopening this issue, as there are still some issues in the handling of IPv6 addresses int he admin console
#7
Comment posted by
lolo4j
Nov 01, 15:34
implemented. Changes committed to SVN trung revision 2527

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.