Hi,
You should add some destination after the wireTap. For example:
from("activemq:queue:aap").wireTap("activemq:queue:aapTap").to(...);
Then you will see that the original flow is processed regardless of the
wireTap flow.
Cheers!
wt., 19.05.2015 o 14:57 użytkownik Jonasty <jonas.audena...@gmail.com>
napisał:
> Hello
> I am monitoring activemq, I use following routebuilder for this:
>
> @Override
> public void configure() throws Exception {
> from("activemq:queue:aap").wireTap("activemq:queue:aapTap");
>
> from("activemq:queue:aapTap").process(myProcessor).id("QueueIncoming");
> }
>
> But when I send manual messages to the queue, they get to the tap queue and
> get consumed on the wireTap, which is ok but also on the original queue,
> which is NOT ok
>
> How can I solve this?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/How-to-wiretap-without-consuming-the-original-queue-tp5767253.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
