0 Replies Latest reply on Jan 4, 2007 7:24 PM by Carl Bailey

    Jboss-4.0.5 port binding problem

    Carl Bailey Newbie

      I am attempting to use a port-bindings.xml file to run multiple jboss instances on a single server, but find that the bindings appear to be not being used by jboss, with no errors being reported, and the server starts perfectly ok but using the default ports.

      I would appreciate any asisstance, have I overlooked anything?

      I start jboss with the standard default server configuration with the additional following definitions on command line:

      -Djboss.bind.address=localhost -Djboss.portbindings.config=ports-01
      

      The jboss-service.xml has the following definition:-
      <mbean code="org.jboss.services.binding.ServiceBindingManager"
       name="jboss.system:service=ServiceBindingManager">
       <attribute name="ServerName">${jboss.portbindings.config}</attribute>
       <attribute name="StoreURL">${jboss.server.config.url}/port-bindings.xml</attribute>
       <attribute name="StoreFactoryClassName">
       org.jboss.services.binding.XMLServicesStoreFactory
       </attribute>
       </mbean>
      

      The boot log shows the port-bindings.xml file being picked up and what appears to be the correct ServiceName
      10:46:23,602 DEBUG [ServiceCreator] About to create bean: jboss.system:service=ServiceBindingManager with code: org.jboss.services.binding.ServiceBindingManager
      10:46:23,628 DEBUG [ServiceCreator] Created bean: jboss.system:service=ServiceBindingManager
      10:46:23,630 DEBUG [ServiceConfigurator] ServerName set to ports-01 in jboss.system:service=ServiceBindingManager
      10:46:23,632 DEBUG [ServiceConfigurator] StoreURL set to file:/jbosssandpit/server/default/conf/port-bindings.xml in jboss.system:service=ServiceBindingManager
      10:46:23,634 DEBUG [ServiceConfigurator] StoreFactoryClassName set to org.jboss.services.binding.XMLServicesStoreFactory in jboss.system:service=ServiceBindingManager
      


      The problem ocurrs in that although the ports have been changed in the xml file, jboss still appears to use the defaults

      10:46:23,878 DEBUG [ServiceCreator] Created bean: jboss:service=Naming
      10:46:23,878 DEBUG [ServiceConfigurator] CallByValue set to false in jboss:service=Naming
      10:46:23,883 DEBUG [ServiceConfigurator] Port set to 1099 in jboss:service=Naming
      10:46:23,885 DEBUG [ServiceConfigurator] BindAddress set to localhost in jboss:service=Naming
      10:46:23,886 DEBUG [ServiceConfigurator] RmiPort set to 1098 in jboss:service=Naming
      10:46:23,888 DEBUG [ServiceConfigurator] RmiBindAddress set to localhost in jboss:service=Naming
      10:46:23,890 DEBUG [ServiceController] recording that jboss:service=Naming depends on jboss.system:service=ThreadPool
      10:46:23,890 DEBUG [ServiceConfigurator] considering LookupPool with object name jboss.system:service=ThreadPool
      


      The relevant entries from the ports-bindings.xml
      <!-- ********************************************************** -->
      <!-- * ports-01 * -->
      <!-- ********************************************************** -->
       <server name="ports-01">
      
       <!-- EJB3 Remoting Connector ejb3.deployer/META-INF/jboss-service.xml -->
      
       <service-config name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"
       delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
       <delegate-config>
       <attribute name="InvokerLocator">socket://${jboss.bind.address}:3973</attribute>
       </delegate-config>
       <binding port="3973"/>
       </service-config>
      
       <!-- ********************* jboss-service.xml ****************** -->
      
       <service-config name="jboss:service=Naming"
       delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
       >
       <delegate-config portName="Port" hostName="BindAddress">
       <attribute name="RmiPort">1198</attribute>
       </delegate-config>
       <binding port="1199" host="${jboss.bind.address}"/>
       </service-config>
       .
       .
       .
       </server>