Yes, it is blocking. The BrokerFilter class implements Broker and simply delegates to the parent Broker so if whatever you are doing is stuck then processing won't continue. If you were to print out a stacktrace from inside one of those methods you will see that there are many BrokerFilter implementations in the chain already to add in various behavior to the broker (logging, authentication, etc)
On Mon, Dec 12, 2016 at 11:23 AM, Devlin <rbasmaj...@ofiglobal.com> wrote: > We're experimenting with BrokerFilter to capture detailed info of producer, > consumer, message headers, etc., for logging and analysis, and want to be > very careful to avoid delaying or blocking the broker. > > If a broker interceptor, for whatever reason, got stuck, would that block a > broker thread from continuing? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Is-BrokerFilter-a-blocking-interceptor-tp4720182.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
