1 Reply Latest reply on Jan 19, 2006 11:40 AM by Bela Ban

    JGroups - Using TCP end_port

    Thomas Wenckebach Newbie

      Hello,
      I want to use group communication via TCP and TCPPING in JBoss 4.0.3SP1. Everything works fine, as long as I don`t use the optional parameter end_port in TCP.

      I definitely cannot tolerate JBoss starting to look itself for free ports if the provided start_port should be already in use - I regard this as an error situation that should prevent JBoss from starting any group communication at all. So I use the following setting in cluster-service.xml:

      <!-- Alternate TCP stack: ... -->
       <Config>
       <TCP start_port="5273" end_port="5275"/>


      This results in the relatively clear message:

      11:38:58,475 ERROR [STDERR] TCP.setProperties(): the following properties are not recognized:
      11:38:58,475 INFO [STDOUT] -- listing properties --
      11:38:58,475 INFO [STDOUT] end_port=5275


      and the accompanying Exception (partly quoted):

      11:38:58,481 WARN [ServiceController] Problem creating service jboss:service=DefaultPartition
      ChannelException: unable to setup the protocol stack
      at org.jgroups.JChannel.<init>(JChannel.java:217)
      at org.jgroups.JChannel.<init>(JChannel.java:189)
      at org.jboss.ha.framework.server.ClusterPartition.createService(ClusterPartition.java:264)



      This sounds like a real bug in JBoss, right? Any solutions?

      Thank you for help -
      regards, Thomas