1 Reply Latest reply on Mar 25, 2006 12:45 PM by starksm64

    tomcat55 port conflict using ServiceBindingManager to unique

    sitkom

      Recently joined a project and my first task is to get multiple instances of
      JBoss 4.0.3SP1 running on a single Win2K machine. I followed the instructions from the wiki http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfiguringMultipleJBossInstancesOnOneMachine .
      I am currently experiencing the same behavior described in this previous post http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3900440 .
      (i.e.) All ports are configured per my sample-bindings.xml except for tomcat55. Tomcat uses the port defined in deploy\jbossweb-tomcat55.sar\server.xml rather the port specified in sample-bindings.xml.
      I copied {jboss.home}\server\default to {jboss.home}\server\node1.
      The jboss-service.xml for both servers contains the mbean-definition for ServiceBindingManager.
      The default server uses "ServerName">ports-default.
      The node1 server uses "ServerName">ports-01.
      I suspect deployment order as mentioned here: http://jira.jboss.com/jira/browse/JBAS-2350 to be a factor.
      But no idea why the config. change did not resolve.
      Any suggestions for further debugging would be appreciated.