Hi all, Our application consists of a lot of seda queues linking all routes and components together. But at the moment it is a bit of a black box, once a message from the JMS goes into a Camel route, there's nothing besides log4j output until the message comes out at the end of the route. Since some of the components might be slow (we've created a one for a slow proprietary system we are using), it is possible that one of the seda queues might be filling up and we need to tweak the number of threads, etc.
So I though about some way to get an overview of all the seda queues in the system and the number of messages waiting in the queues. One possibility would be to create a static SedaRegister class where every SedaProducer registers itself upon instantiation. Via this register any class inside the same JVM could query the seda queues and write the state to a textfile, a database, or some management console. Or a JMX wrapper around this register. Another possibility would be to have a static Map where every SedaProducer writes its name and number of messages to, everytime a message is added to/removed from the queue. Or is there something in Camel already to achieve this? Thanks, Arjan -- View this message in context: http://www.nabble.com/Inspecting-seda-queues-tp14685106s22882p14685106.html Sent from the Camel - Users mailing list archive at Nabble.com.
