3:05 a.m.
JmsConnectionPool swallows NamingException
------------------------------------------
Key: JBESB-2493
URL: https://jira.jboss.org/jira/browse/JBESB-2493
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.4 CP2
Reporter: Jiri Pechanec
Assignee: Kevin Conner
See the following code
try
{
factoryConnection = jndiContext.lookup(connectionFactoryString);
} catch (NamingException ne) {
logger.info("Received NamingException, refreshing
context.");
jndiContext = NamingContextPool.replaceNamingContext(jndiContext,
JmsConnectionPoolContainer.getJndiEnvironment(poolKey));
factoryConnection = jndiContext.lookup(connectionFactoryString);
}
If the exception is thrown it is not logged and there is no way to identify the reason of
error
--
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:05 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2493) JmsConnectionPool swallows NamingException
[
https://jira.jboss.org/jira/browse/JBESB-2493?page=com.atlassian.jira.plu...
]
Jiri Pechanec updated JBESB-2493:
---------------------------------
Component/s: Rosetta
JmsConnectionPool swallows NamingException
------------------------------------------
Key: JBESB-2493
URL: https://jira.jboss.org/jira/browse/JBESB-2493
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Jiri Pechanec
Assignee: Kevin Conner
See the following code
try
{
factoryConnection = jndiContext.lookup(connectionFactoryString);
} catch (NamingException ne) {
logger.info("Received NamingException, refreshing
context.");
jndiContext = NamingContextPool.replaceNamingContext(jndiContext,
JmsConnectionPoolContainer.getJndiEnvironment(poolKey));
factoryConnection = jndiContext.lookup(connectionFactoryString);
}
If the exception is thrown it is not logged and there is no way to identify the reason of
error
--
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:29 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2493) JmsConnectionPool swallows NamingException
[
https://jira.jboss.org/jira/browse/JBESB-2493?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2493:
-------------------------------------
This is intentional as there is an attempt to re-establish the JNDI context and factory
connection.
What problem are you seeing with this?
JmsConnectionPool swallows NamingException
------------------------------------------
Key: JBESB-2493
URL: https://jira.jboss.org/jira/browse/JBESB-2493
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Jiri Pechanec
Assignee: Kevin Conner
See the following code
try
{
factoryConnection = jndiContext.lookup(connectionFactoryString);
} catch (NamingException ne) {
logger.info("Received NamingException, refreshing
context.");
jndiContext = NamingContextPool.replaceNamingContext(jndiContext,
JmsConnectionPoolContainer.getJndiEnvironment(poolKey));
factoryConnection = jndiContext.lookup(connectionFactoryString);
}
If the exception is thrown it is not logged and there is no way to identify the reason of
error
--
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:42 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2493) JmsConnectionPool swallows NamingException
[
https://jira.jboss.org/jira/browse/JBESB-2493?page=com.atlassian.jira.plu...
]
Jiri Pechanec commented on JBESB-2493:
--------------------------------------
I am configuring ESB with WS MQ - unfortunately I am getting this in log
2009-03-30 03:14:44,090 INFO
[org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool] Received NamingException,
refreshing context.
2009-03-30 03:14:44,092 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] Caught service
lookup exception for EPR [JMSEpr [ PortReference < <wsa:Address
jms://localhost:1099/queue/pt_helloworld_esb/>, <wsa:ReferenceProperties
jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>,
<wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://localhost:1099/>,
<wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs :
org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties
jbossesb:destination-type : queue/>, <wsa:ReferenceProperties
jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties
jbossesb:connection-factory : WSConnectionFactory/>, <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 [simple:CUSTOM] and Message [header: [ To: JMSEpr [ PortReference <
<wsa:Address jms://localhost:1099/queue/pt_helloworld_esb/>,
<wsa:ReferenceProperties jbossesb:java.naming.factory.initial :
org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties
jbossesb:java.naming.provider.url : jnp://localhost:1099/>, <wsa:ReferenceProperties
jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>,
<wsa:ReferenceProperties jbossesb:destination-type : queue/>,
<wsa:ReferenceProperties jbossesb:specification-version : 1.1/>,
<wsa:ReferenceProperties jbossesb:connection-factory : WSConnectionFactory/>,
<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/> > ] ]]. Failed to get JMS Session from pool.
2009-03-30 03:14:44,092 INFO [org.jboss.soa.esb.client.ServiceInvoker] Unresponsive EPR:
JMSEpr [ PortReference < <wsa:Address
jms://localhost:1099/queue/pt_helloworld_esb/>, <wsa:ReferenceProperties
jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>,
<wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://localhost:1099/>,
<wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs :
org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties
jbossesb:destination-type : queue/>, <wsa:ReferenceProperties
jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties
jbossesb:connection-factory : WSConnectionFactory/>, <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/> > ] for
message: header: [ ]
2009-03-30 03:14:44,092 INFO [org.jboss.soa.esb.client.ServiceInvoker] Delivering message
[header: [ ]] to RDLVRQ.
and the messages are not process. It is very difficult to identify the root of problem if
the original message is not available on DEBUG/TRACE level
JmsConnectionPool swallows NamingException
------------------------------------------
Key: JBESB-2493
URL: https://jira.jboss.org/jira/browse/JBESB-2493
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Jiri Pechanec
Assignee: Kevin Conner
See the following code
try
{
factoryConnection = jndiContext.lookup(connectionFactoryString);
} catch (NamingException ne) {
logger.info("Received NamingException, refreshing
context.");
jndiContext = NamingContextPool.replaceNamingContext(jndiContext,
JmsConnectionPoolContainer.getJndiEnvironment(poolKey));
factoryConnection = jndiContext.lookup(connectionFactoryString);
}
If the exception is thrown it is not logged and there is no way to identify the reason of
error
--
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:57 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2493) JmsConnectionPool swallows NamingException
[
https://jira.jboss.org/jira/browse/JBESB-2493?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2493:
-------------------------------------
So the issue here is that the *caller* of this is swallowing the naming exception.
That code makes a second attempt to retrieve the JNDI context/factory connections and any
permanent errors will result in an exception being thrown from the attempt within the
catch.
In this case that would be ServiceInvoker which is at fault.
In fact, the SI code which logs the debug is not even checking to see whether debug is
enabled or not.
JmsConnectionPool swallows NamingException
------------------------------------------
Key: JBESB-2493
URL: https://jira.jboss.org/jira/browse/JBESB-2493
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Jiri Pechanec
Assignee: Kevin Conner
See the following code
try
{
factoryConnection = jndiContext.lookup(connectionFactoryString);
} catch (NamingException ne) {
logger.info("Received NamingException, refreshing
context.");
jndiContext = NamingContextPool.replaceNamingContext(jndiContext,
JmsConnectionPoolContainer.getJndiEnvironment(poolKey));
factoryConnection = jndiContext.lookup(connectionFactoryString);
}
If the exception is thrown it is not logged and there is no way to identify the reason of
error
--
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:59 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2493) ServiceInvoker swallows exceptions
[
https://jira.jboss.org/jira/browse/JBESB-2493?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2493:
--------------------------------
Summary: ServiceInvoker swallows exceptions (was: JmsConnectionPool swallows
NamingException)
ServiceInvoker swallows exceptions
----------------------------------
Key: JBESB-2493
URL: https://jira.jboss.org/jira/browse/JBESB-2493
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Jiri Pechanec
Assignee: Kevin Conner
See the following code
try
{
factoryConnection = jndiContext.lookup(connectionFactoryString);
} catch (NamingException ne) {
logger.info("Received NamingException, refreshing
context.");
jndiContext = NamingContextPool.replaceNamingContext(jndiContext,
JmsConnectionPoolContainer.getJndiEnvironment(poolKey));
factoryConnection = jndiContext.lookup(connectionFactoryString);
}
If the exception is thrown it is not logged and there is no way to identify the reason of
error
--
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
5:34 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2493) ServiceInvoker swallows exceptions
[
https://jira.jboss.org/jira/browse/JBESB-2493?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2493:
--------------------------------
Fix Version/s: 4.4 CP3
ServiceInvoker swallows exceptions
----------------------------------
Key: JBESB-2493
URL: https://jira.jboss.org/jira/browse/JBESB-2493
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Fix For: 4.4 CP3
See the following code
try
{
factoryConnection = jndiContext.lookup(connectionFactoryString);
} catch (NamingException ne) {
logger.info("Received NamingException, refreshing
context.");
jndiContext = NamingContextPool.replaceNamingContext(jndiContext,
JmsConnectionPoolContainer.getJndiEnvironment(poolKey));
factoryConnection = jndiContext.lookup(connectionFactoryString);
}
If the exception is thrown it is not logged and there is no way to identify the reason of
error
--
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
4:05 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-2493) ServiceInvoker swallows exceptions
[
https://jira.jboss.org/jira/browse/JBESB-2493?page=com.atlassian.jira.plu...
]
Work on JBESB-2493 started by Kevin Conner.
ServiceInvoker swallows exceptions
----------------------------------
Key: JBESB-2493
URL: https://jira.jboss.org/jira/browse/JBESB-2493
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Fix For: 4.4 CP3
See the following code
try
{
factoryConnection = jndiContext.lookup(connectionFactoryString);
} catch (NamingException ne) {
logger.info("Received NamingException, refreshing
context.");
jndiContext = NamingContextPool.replaceNamingContext(jndiContext,
JmsConnectionPoolContainer.getJndiEnvironment(poolKey));
factoryConnection = jndiContext.lookup(connectionFactoryString);
}
If the exception is thrown it is not logged and there is no way to identify the reason of
error
--
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
4:26 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-2493) ServiceInvoker swallows exceptions
[
https://jira.jboss.org/jira/browse/JBESB-2493?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-2493.
-------------------------------
Resolution: Done
Updated in revision 26608.
ServiceInvoker swallows exceptions
----------------------------------
Key: JBESB-2493
URL: https://jira.jboss.org/jira/browse/JBESB-2493
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Fix For: 4.4 CP3
See the following code
try
{
factoryConnection = jndiContext.lookup(connectionFactoryString);
} catch (NamingException ne) {
logger.info("Received NamingException, refreshing
context.");
jndiContext = NamingContextPool.replaceNamingContext(jndiContext,
JmsConnectionPoolContainer.getJndiEnvironment(poolKey));
factoryConnection = jndiContext.lookup(connectionFactoryString);
}
If the exception is thrown it is not logged and there is no way to identify the reason of
error
--
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
5715
days inactive
5765
days old
8 comments
2 participants
participants (2)
-
Jiri Pechanec (JIRA) -
Kevin Conner (JIRA)