JMS Broker Reconnect Issue.
- From: "Steve" <steve.scandore@xxxxxxxxxxxx>
- Date: Wed, 4 May 2005 15:34:56 -0700
I need to introduce a JMS reconnect feature into an existing application.
Basically, the application is a simple consumer of messages from a JMS
topic. My requirement is to have the application continue to consume
messages after the connected JMS service is restarted. I detect the failed
JMS service through the ExceptionListener callback. Once detected, I go into
a reconnect loop.
The reconnect loop attempts to make the JMS connections once every minute
until the JMS service is again available. Obviously, it will fail if the
service has not come back yet. That's not the problem. The problem is:
1. The JNDI lookups continually fail after the service is back. Note: I am
using a Sun One Appserver 7 with both the JNDI and JMS all in one. When I
say "service is back", I mean both the JNDI and the JMS service are up and
running.
2. I do something like this:
context = new InitialContext();
factory = (TopicConnectionFactory) context.lookup("abc");
This works when the application first comes up, but fails when trying it
after the Appserver (JNDI/JMS) is restarted. Is there something lingering
that prevents these calls from working?
My question is: What is required to get this to work? Is this approach an
acceptable recovery solution? Thanks in advance for any help.
Steve
.
- Prev by Date: Re: J2EE tutorial (Learn J2EE in 21 Days, Sam's)
- Next by Date: Re: what is assertion in java?
- Previous by thread: Re: how to run 2 thread with different code
- Next by thread: Re: what is assertion in java?
- Index(es):
Relevant Pages
|
|
