Unable to restrict JGroups TCP to bind to one and only one specific port in EAP 6

Solution Verified - Updated -

Issue

  • For security reasons, we have to restrict and control all binding port used by the application. For JGroups we are using TCP and TCPING protocols. We noted that if the port specified in the binding sockets of the TCP protocol is used, jgroups will try to bin port+1 and so on. We try to add a property end_port but this property is not recognized.

  • How can one specify the TCP end_port property for a JGroups TCP transport in EAP 6 ? In EAP 5.1, we could do something like this:
    <TCP singleton_name="tcp" start_port="7600" end_port="7604"/> to indicate that JGroups should try to bind to 7600. If that doesn't succeed, it should try 7601, 7602, etc. until the specified end_port. In EAP 6 however, the 'socket-binding' property is used to define the socket to bind to, but I can't find a mechanism to specify that end_port property. Does someone know how to configure that on EAP 6 ?

Environment

JBoss Enterprise Application Platform (EAP) 6.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.