« Return to Thread: JMS + SimpleRetryConnectionStrategy +JNDI +OracleJMS ... not working

Re: JMS + SimpleRetryConnectionStrategy +JNDI +OracleJMS ... not working

by Andrew Perepelytsya :: Rate this Message:

Ken,

I think you're right, the JNDI connection is not recycled. Note however, this is not a full explanation. Most probably it's very implementation-specific, e.g. I had similar symptoms (unable to recover) with JBoss when running in HA/clustered mode with HA-JNDI, but it worked flawlessly with normal JNDI.

I've filed http://mule.mulesource.org/jira/browse/MULE-1416 for this.

Andrew

On 2/21/07, kennywest <kenneth.westelinck@...> wrote:

I've done some further digging. The JNDI context is created near
initJndiContext() in JMSMessageConnector. This is only called from the
doConnect(), if connectionFactory == null method.
If somewhere the connection with the JNDI store is lost, the jndiContext
member will fail when doing getJndiDestination() in Jms11Support.
Therefore the reconnect strategy does not cover loss of connections with
JNDI stores. Am I correct?

Pleas note, I am not criticizing anything, just looking for the right
solution ;)

--
View this message in context: http://www.nabble.com/JMS-%2B-SimpleRetryConnectionStrategy-%2BJNDI-%2BOracleJMS-...-not-working-tf3265566.html#a9082171
Sent from the Mule - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

« Return to Thread: JMS + SimpleRetryConnectionStrategy +JNDI +OracleJMS ... not working