[JBoss JIRA] Created: (JBESB-2519) ServiceClient hides some errors which makes debugging config problems difficult
10:02 a.m.
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
10:04 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2519) ServiceClient hides some errors which makes debugging config problems difficult
[
https://jira.jboss.org/jira/browse/JBESB-2519?page=com.atlassian.jira.plu...
]
toby cabot updated JBESB-2519:
------------------------------
Attachment: exception-patch.txt
patch to make ServiceInvoker log CourierServiceBindExceptions thrown by the courier.
provides useful info for debugging misconfigured servers.
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
Attachments: exception-patch.txt
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
3:46 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2519) ServiceInvoker swallows exceptions
[
https://jira.jboss.org/jira/browse/JBESB-2519?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2519:
--------------------------------
Summary: ServiceInvoker swallows exceptions (was: ServiceClient hides some
errors which makes debugging config problems difficult)
Fix Version/s: 4.6
Hiya Tony.
I recently logged JBESB-2493 to handle this very issue but that is currently logged
against the 4.4 CP branch. I have modified this report and linked it into the work for
the next 4.6 release.
Thanks for the report.
Kev
ServiceInvoker swallows exceptions
----------------------------------
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
Fix For: 4.6
Attachments: exception-patch.txt
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
3:48 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2519) ServiceInvoker swallows exceptions
[
https://jira.jboss.org/jira/browse/JBESB-2519?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2519:
-------------------------------------
Sorry, checking the issue shows that Jirka logged it and not me :)
ServiceInvoker swallows exceptions
----------------------------------
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
Fix For: 4.6
Attachments: exception-patch.txt
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
2:22 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2519) ServiceInvoker swallows exceptions
[
https://jira.jboss.org/jira/browse/JBESB-2519?page=com.atlassian.jira.plu...
]
Daniel Bevenius reassigned JBESB-2519:
--------------------------------------
Assignee: Daniel Bevenius
ServiceInvoker swallows exceptions
----------------------------------
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
Assignee: Daniel Bevenius
Priority: Minor
Fix For: 4.6
Attachments: exception-patch.txt
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
2:34 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-2519) ServiceInvoker swallows exceptions
[
https://jira.jboss.org/jira/browse/JBESB-2519?page=com.atlassian.jira.plu...
]
Daniel Bevenius closed JBESB-2519.
----------------------------------
Resolution: Done
Committed revision 26629.
ServiceInvoker swallows exceptions
----------------------------------
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
Assignee: Daniel Bevenius
Priority: Minor
Fix For: 4.6
Attachments: exception-patch.txt
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
5524
days inactive
5561
days old
5 comments
3 participants
participants (3)
-
Daniel Bevenius (JIRA) -
Kevin Conner (JIRA)
-
toby cabot (JIRA)