activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Mielke <tmie...@redhat.com>
Subject Re: Messages stuck, back to normal after restart
Date Thu, 07 Nov 2013 08:43:44 GMT
Hello,

Are you using broker networks? If yes, please have a read over 
http://tmielke.blogspot.de/2012/03/i-have-messages-on-queue-but-they-dont.html
The fact that you cannot even browse the messages got me wonder if you use broker networks.


Do your consumers use message selectors by any chance and hence don't consume all the messages?
What happens if you attach another external consumer to these destinations? Will they consume
the outstanding messages? Very likely not, if you cannot even browse these messages. 

You could try with a more recent broker version (e.g. 5.9.0), perhaps running it external
to the ServiceMix installation.



Regards,


Torsten Mielke
tmielke@redhat.com
tmielke.blogspot.com



On Nov 6, 2013, at 15:14 PM, cristisor wrote:

> Hi all,
> 
> We are using Apache ServiceMix 3.6.0-fuse-00-89 with ActiveMQ
> 5.5.1-fuse-00-89. Lately, a very weird problem has been reported, the
> messages don't arrive to the consumers. The messages are being sent from
> different machines, each with its own topic, and each topic has 2
> subscriptions. One subscription is being used by a Java application running
> as a Windows Service and the other one is being used by an Apache Camel
> component.
> 
> The load is not very high, so we don't consider memory/resources problems.
> Also, the number of stuck messages is pretty high, 980 messages out of 1433
> reached one of the endpoints and 1288 out of 1433 reached the other endpoint
> yesterday. An average of 1500 messages per day is not much at all and can't
> cause memory issues.
> 
> After restarting ServiceMix (with the embedded broker), most of the messages
> got through, but a second restart was necessary to have everything sent. I'm
> using JConsole so I tried to browse the messages on that endpoint, but a
> blank window was shown.
> 
> The only thing that has changed between the releases is the ack mode, from
> DUPS_OK_ACKNOWLEDGE to AUTO_ACKNOWLEDGE now.
> 
> This problems is random and the situation is pretty bad because it's the
> production environment, so any help would be apreciated.
> 
> Thanks.
> 
> 
> 
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Messages-stuck-back-to-normal-after-restart-tp4673949.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message