[esb-issues] [JBoss JIRA] Commented: (JBESB-1555) Investigate ServiceInvoker/policy behaviour

Investigate ServiceInvoker/policy behaviour ------------------------------------------- Key: JBESB-1555 URL: http://jira.jboss.com/jira/browse/JBESB-1555 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Kevin Conner Fix For: 4.2.1 CP2, 4.3 Attachments: ServiceInvoker-loadbalance.tar.gz From Noel. Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in the load balancing behaviour. I've got a very simple use case with a service deployed into 2 nodes and sending 2 messages only. With a debugger, I can see that the two EPR are used by the ServiceInvoker and that the RoundRobin Policy that I've set is used to choose alternatively each one. However, I can see that the same JMS connection properties are reused (by JMSCourier) instead of having the properties extracted from the second EPR. Is there a way for you to check this ? ------------------------------------------------ I forgot to mention that I'm sending messages to esb services from a standalone JSE java application with the ServiceInvoker. Going further, I can see that the EPR's <wsa:address .../> value is not used to initialise the JMS connection. <ReferenceProperties /> are used instead. This problem happens when the jndi-url is not setup for your esb service (because you want to use the default value defined for your esb node in the jbossesb.sar/jbossesb-properties.xml). Then you have two ways to fix this : - when declaring the EPR, reuse the wsa:address values when nothing is defined for the provider (JMS) - when the service invoker is creating the JMS connection to send the message, use the <wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part