• Bug
  • Status: Closed
  • Resolution: Fixed
  • drb
  • Reporter: sourceforgetracker
  • September 21, 2009
  • 0
  • Watchers: 1
  • September 22, 2009
  • September 22, 2009


The RMICacheManagerPeerListenerFactory allows a port to be configured; unfortunately, contrary to what the docs in the ehcache.xml seem to indicate, this does not configure the port the peer listens on, but instead only configures the port the rmi-registry listens on. The port the peer listens on is not configurable and is assigned a random port (line 60 of RMICachePeer, first parameter to super()), preventing this from working through firewalls.

In short, we’d like to be able to configure the peer-listener port too.

Sourceforge Ticket ID: 1887683 - Opened By: roadrunner2 - 6 Feb 2008 08:15 UTC


Fiona OShea 2009-09-22

Re-opening so that I can properly close out these issues and have correct Resolution status in Jira