[esb-issues] [JBoss JIRA] (JBESB-3959) ServiceInvoker spans multiple nodes when gateway and esb queue are both defined as non clustered

ServiceInvoker spans multiple nodes when gateway and esb queue are both defined as non clustered ------------------------------------------------------------------------------------------------ Key: JBESB-3959 URL: https://issues.jboss.org/browse/JBESB-3959 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 4.11 Environment: Linux Reporter: Dave Siracusa Messages are crossing server boundaries in a multi-server cluster even though queues are defined as non-clustered. Enqueuing a message only to the first server node is accepted by the first server, and is routed in round robin fashion to each server in the cluster. The reason for this is that during ESB deployment RegistryUtil.register(_config, _epr) is called when it resolves the epr via jmsEprFromElement. The jndi url is resolved via Configuration.getJndiServerURL(). This returns the hostname, so the registered EPR in JUUDI includes host specific EPR entries. The ServiceInvoker appears to route in round robin fashion to each registered entry. Inspecting our older/existing SOA 5.2.0 yields a jnp address which happen to reflect the -b (bind address) we specify (in our case 0.0.0.0). The registration process between SOA 5.2.0 and SOA 5.3.1 differ, where the default behavior in SOA 5.3.1 registration is to register services for use and available to all other node regardless of queue isolation settings and bind address. A combination of clustered and non-clustered queues will likely have problems.