We have a bit more context from this request from the ActiveMQ mailing list (double posted) and elsewhere on this list. As far as I can tell, they are merely trying to "monitor" (meaning log to a database) all messages coming out of one queue. That's why I asked if the consumer is a camel route already. If so, merely doing wiretap is a quick and easy way to achieve what they were looking to do. If they are looking for a more comprehensive monitoring and statistics approach, then no way would you want to inject that into all your camel routes using the wiretap DSL. But, if it's for one particular queue and one particular route, sure.
On Wed, Mar 25, 2015 at 3:41 PM, Greg Autric <gaut...@redhat.com> wrote: > Hi, James, > > Using wiretap is an anti-pattern 'cause you have to change your camel route > to inject the wiretap component. > Monitoring and statistic management should be outside of the camel route. > The intercept process will "copy" the message if and only if this message is > consume via the JMS component. > > > Greg AUTRIC > JBoss Middleware Consultant > > email : gautric __at__ redhat __dot__ com > twitter : @gautric_io > > ----- Mail original ----- > De: "James Carman" <ja...@carmanconsulting.com> > À: users@camel.apache.org > Envoyé: Mercredi 25 Mars 2015 17:51:57 > Objet: Re: Apache camel monitor activemq > > Is it a Camel route that's consuming the messages eventually? If so, > you can "wiretap" the messages off and log them if you want. > > http://camel.apache.org/wire-tap.html
