Just because the messages should get consumed doesn't mean they are being 
consumed.

And even if they are being consumed it doesn't mean they are being consumed at 
the same rate as they are being sent.

The most likely cause here is you are sending messages fasting than you are 
consuming them, consequently they will build up on the queue or subscription, 
until the system runs out of storage for them.

As I say, if there is an underlying problem here then you should be able to 
replicate it in a test and that will give us something to start from.

But first you need to validate you're not sending messages fasting than you're 
consuming.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947410#3947410

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947410


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to