activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From semog <>
Subject Re: Nms Reconnect
Date Thu, 20 Nov 2008 01:41:38 GMT

We are also having message flow problems, but our problems are with a 100%
Java solution.  No NMS or .NET stuff in the mix.  Our current suspects are
either ActiveMQ 5.1.0 or JBOSS, or some combination thereof.  Like you, we
can get messages to go for a while, and then the consumer just stops getting
new messages.  The producer can still send messages, though.  It's very odd
and frustrating.  A couple of guys on my team are working on tracking it

mkeenan wrote:
> Bryan Murphy-4 wrote:
>> What do I need to do to ensure that our .NET clients will reliably
>> re-connect to the server when I bounce it?
> You might want to take a look at the Spring.NET source code.  I'm using
> message listener containers and they survive an AMQ broker bounce because
> there is reconnect logic in that code. You can set the frequency and
> timeout to attempt reconnect as often as you want for as long as you want. 
> The Spring.Messaging.NMS namespace is relatively small, so hopefully the
> effort to find and extract the pieces you might want would be minimal.
> Having said that, we are having our own significant challenges with
> reliable messaging.  I don't know where the problem is [our code,
> Spring.NET, or NMS] so I can't open any useful JIRA just yet.  The biggest
> issue is that messages stop flowing and we either have to restart AMQ or
> restart our service (which produces and consumes) in order to get the
> messages going again.

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message