Hi
You could also browse the queue and see how old the first message is. If its more than 5 minutes old than the consumers isn't accepting the message, in a timerly manner. http://activemq.apache.org/camel/browsableendpoint.html And since its JMS you have the QueueBrowser interface if I recall correctly. And in the bigger picture then I am pretty sure some of the nifty monitoring systems can track this metric and start sending alers etc. Maybe the hyperic guys have a demo of this? But again if you have a simple need maybe it can be solved more easily in Camel. Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: sub3 [mailto:[EMAIL PROTECTED] Sent: 12. juni 2008 18:43 To: [email protected] Subject: JmsComponent, client dying 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.
