JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-198  -  Issues with multi-server topologies
Posted Nov 15, 2013 - updated Dec 27, 2014
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
    High
  • Reproducability
    Not determined
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.3.x
Issue description
There are several issues when using topologies with multiple servers connected in p2p:
  1. one is reported in this forum thread. This is potentially a regression due to the fix of Bug report JPPF-186 - SSL services unable to distinguish between client and node certificates, where we might have overlooked that the peer identifier is no longer sent via SSL
  2. another one that I have identified, which is a regression from Enhancement JPPF-183 - Add relevant classes cache lookups in the driver


Steps to reproduce this issue
  • for 1. use a p2p setup with SSL enabled between servers
  • for 2. use a p2p setup without SSL

#5
Comment posted by
lolo4j
Nov 17, 08:16
Fix committed to: