activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From oliverd <oliver.deck...@hotmail.com>
Subject Destination LoggingBrokerPlugin advisoryForConsumed
Date Mon, 02 Jun 2014 07:15:14 GMT
some Destination interface methods, e.g. messageConsumed, are coupled in
org.apache.activemq.broker.region.BaseDestination to AdvisoryMessages flags,
e.g. advisoryForConsumed.

This way, other plugins like LoggingBrokerPlugin are not called

is there a special reason for this coupling?

actually, what I tried is to get triggered for message consumption on
inidividual queues using an own broker plugin - but, Queue.acknowledge()
calls BaseDestination.messageConsumed() which checks for advisoryForConsumed
that means, this works only if advisoryForConsumed is activated (firing on
every single message)




--
View this message in context: http://activemq.2283324.n4.nabble.com/Destination-LoggingBrokerPlugin-advisoryForConsumed-tp4681563.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message