[esb-issues] [JBoss JIRA] Updated: (JBESB-2060) ServiceInvoker fails to find HAJNDI when invoked in clustered environment

ServiceInvoker fails to find HAJNDI when invoked in clustered environment ------------------------------------------------------------------------- Key: JBESB-2060 URL: https://jira.jboss.org/jira/browse/JBESB-2060 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Registry and Repository, Rosetta, Transports Affects Versions: 4.2.1 CP2 Environment: SOA-P and Fedora9 Linux Reporter: Magesh Kumar B Fix For: 4.2.1 CP5 Create two instances of SOA-P in Linux platform using the ports binding service. Start the two instances. Change the InquiryURI and PublishURI as below in jbossesb-properties.xml inside samples/quickstarts/helloworld: <property name="org.jboss.soa.esb.registry.queryManagerURI" value="jnp://127.0.0.1:1100/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire"/> <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI" value="jnp://127.0.0.1:1100/PublishService?org.apache.juddi.registry.rmi.Publish#publish" /> Notice they use HAJNDI ports. Deploy Quicktsart_helloworld_esb and run "ant sendesb", the test fails with exception: sendesb: [echo] Runs Test ESB Message Sender [java] Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message [header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors. [java] at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:356) [java] at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:225) [java] at org.jboss.soa.esb.client.ServiceInvoker.deliverToDeadLetterService(ServiceInvoker.java:267) [java] at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:235) [java] at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage.main(SendEsbMessage.java:55) However, this only happens in Linux enviornment (Fedora9 in my test) and passes in Windows. Also the HAJNDI port 1100 works if only one instance is running in that cluster partition. When we use these ports 1100/1200 in JMS client and do "ant runtest", they connect seamlessly.