1 Reply Latest reply on Nov 8, 2004 3:57 PM by Joel Rosi-Schwartz

    ServiceBindingManager and JMS -  Address Conflicts in JBOSS

    Piero Colagrosso Newbie

      Hi,

      I am using the ServiceBindingManager configuration to run multiple JBOSS instances on a single machine. The application makes use of JMS and is actually being ported from JBOSS 3.2.5 to JBOSS 4.0

      With the default configuration, everything works well (after having copied over the missing bindingservice-plugin.jar into my config's lib directory).

      With the standard configuration, I am getting 'Address already In Use' error messages relating to the OIL and OIL2 services:

       Problem starting service jboss.mq:service=InvocationLayer,type=OIL java.net.BindException: Address already in use
      ...


      In order to get rid of these error messages I had to add the following types of entries (for each of ports-01, ports-02, etc...) to the file $JBOSS_HOME/docs/examples/binding-manager.

      <service-config name="jboss.mq:service=InvocationLayer,type=OIL2"
       delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
       >
       <delegate-config portName="ServerBindPort"/>
       <binding port="8192"/>
       </service-config>
      
       <service-config name="jboss.mq:service=InvocationLayer,type=OIL"
       delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
       >
       <delegate-config portName="ServerBindPort"/>
       <binding port="8190"/>
       </service-config>


      Is this a known problem with the sample-bindings.xml file when using the standard configuration in JBOSS 4.0?

      Thanks,

      Piero

      Note: In the course of migrating from JBOSS 3.2.5 to JBOSS 4.0 I have switched from the default config to the standard config in order to preserve the class loading and the intra-JVM call by reference invocation semantics which I've grown used to in JBOSS 3.2.x.