stom check to see if messages need to be intercepted
> letPass = false;
> }
> }
> return letPass;
> }
>
> }
>
> Hannes
>
>
>
> Gesendet: Samstag, 20. November 2021 um 00:43 Uhr
> Von: "Justin Be
rn letPass;
}
}
Hannes
Gesendet: Samstag, 20. November 2021 um 00:43 Uhr
Von: "Justin Bertram"
An: users@activemq.apache.org
Betreff: Re: Re: pause acceptance and delivery of messages in ActiveMQ 5.16.3
I'm confused about the nature of your use-case. You originally said tha
I'm confused about the nature of your use-case. You originally said that
you were using ActiveMQ 5.16.3, but in this latest email you mention
intercepting things like ClusterTopologyChangeMessage_V4,
CreateSessionMessage_V2, CreateSessionResponseMessage, etc. which are used
exclusively by ActiveMQ
Thank you very much for the possible solutions.
I finally was able to try the approach with the interceptor and it works great
for intercepting messages send to the broker using SessionSendMessage to filter
the messages I want to intercept.
Unfortunately, it does not intercept messages sent from
The success of that approach would depend on how OP's clients are
interacting with the broker.
If all producers are OpenWire connect and stay connected forever with no
disconnects and no producers coming and going, then this manual process
could work. If producers come and go (including due to aut
Isn't it also possible to stop the client connector via JMX?
org.apache.activemq:type=Broker,brokerName=esb-test-mq04.it.su.se,connector=clientConnectors,connectorName=ssl
has a stop operation.
Does this not work the way OP intends?
Pause queue(s), stop connector(s). No messages in or out?
B
I believe it would be possible to write a custom interceptor (see
https://activemq.apache.org/interceptors) that rejected incoming messages
and incoming connections. (Maybe rejecting incoming connections would be
enough, because you can't send a message without an established
connection.) If you re
