[esb-issues] [JBoss JIRA] Created: (JBESB-2519) ServiceClient hides some errors which makes debugging config problems difficult

ServiceClient hides some errors which makes debugging config problems difficult ------------------------------------------------------------------------------- Key: JBESB-2519 URL: https://jira.jboss.org/jira/browse/JBESB-2519 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: toby cabot Priority: Minor I accidentally mis-configured a node with a "-b" bind address of "0.0.0.0". This causes a pretty obvious problem for other nodes that want to connect to it - they try to connect to themselves. Unfortunately ServiceClient swallows the error data and just emits "Failed to get JMS Session from pool" which can have 3 different causes. For example: 2009-04-13 09:52:30,937 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] Caught service lookup exception for EPR [JMSEpr [ PortReference < <wsa:Address jms://10.18.2.178:1099/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.18.2.178:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]] and Service [JBossESB-Internal:DeadLetterService] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://10.18.2.178:1099/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.18.2.178:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 05576e08-115c-4233-b417-262b7b174c47 RelatesTo: jms:correlationID#05576e08-115c-4233-b417-262b7b174c47 ]]. Failed to get JMS Session from pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira