Often queue size is a good indicator of a consumer having problems; so you could monitor that and throttle/stop the sender when a queue size grows beyond a certain size. You can set alerts like this in Hyperic.
BTW another approach is to use the consumer advisories to watch if a consumer on a queue dies; but the queue size is usually the best indicator of things http://activemq.apache.org/advisory-message.html There's a ConsumerEventSource helper class in the org.apache.activemq.advisory package that can help with tracking consumers btw. 2008/6/12 sub3 <[EMAIL PROTECTED]>: > > I have a module that slowly dies, eventually running out of memory. I want > to trap this from the sender side & report. > > From this module, I can see him taking a message & eventually stopping, so > it never accepts another message. > From the server side (the sender), the queue fills up and can't send > anymore. I want the server/sender side to be notified of this failure. Is > there a way, like a timeout after not being able to send after 5 minutes? > > I've seen several parameters for the JmsComponent, like receiveTimeout; but > I don't want this code on the client side, it already knows it is dying. > > -- > View this message in context: > http://www.nabble.com/JmsComponent%2C-client-dying-tp17804357s22882p17804357.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
