1 Reply Latest reply on Apr 3, 2013 6:47 PM by welsh

    JBoss AS 5.1 Port Conflicts when above 10 port sets

    welsh Newbie



      I'm running into an issue with bindings-jboss-beans.xml when modifying it to use more than 10 port sets.


      What I've found is this port binding:


      <bean class="org.jboss.services.binding.ServiceBindingMetadata">

              <property name="serviceName">jboss:service=invoker,type=pooled</property>

              <property name="port">4445</property>

              <property name="description">Socket for the legacy Pooled invoker</property>



      Conflicts with this port binding:


      <bean class="org.jboss.services.binding.ServiceBindingMetadata">

              <property name="serviceName">HornetQ</property>

              <property name="bindingName">netty-port</property>

              <property name="port">5445</property>

              <property name="description">Socket for HornetQ</property>



      On a port binding of +1000 or greater when port sets below it are running. IE ports-default (+0) on 4445 / 5445 conflicts with ports10 (+1000) which runs 5445 /6445.


      I've looked through and I think I can update the Legacy Pooled Invoker Binding to 4442 since I cant find a binding ending in 442 that could cause a conflict.


      Nothing is currently bound to 4442 incrementing by 100 to 6442 with +0 to +900 running right now. (I'm looking to get 20 port sets on one box).


      Was wondering if anyone else had any experience with this and used a similiar solution.