I believe it's because it's not implemented.
I did a small modification to the code to test this hypothesis:
https://github.com/orpiske/activemq-artemis/commit/bd57548b6b2897a436240d6abadc1a8e01a1acc9.
After that, it can intercept Connect control packets.
On Thu, Aug 10, 2017 at 2:00 PM, aragoubi <aymen....@gmail.com> wrote:
> I added an mqtt interceptor into my artemis broker in order to intercept
> mqtt
> client connection:
>
>
>
> /public class SimpleMQTTInterceptor implements MQTTInterceptor
> {
> @Override
> public boolean intercept(final MqttMessage mqttMessage,
> RemotingConnection
> connection) throws ActiveMQException
> {
> System.out.println("MQTT Interceptor gets called ");
>
> if (mqttMessage instanceof MqttConnectMessage)
> {
> System.out.println("MQTT connection intercepted ");
> }
> return true;
> }
> }/
>
> My problem is that only message published to topics are intercepted.
> Why this doesn't intercept *CONNECT* message ?
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Intercept-mqtt-client-connection-tp4729594.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
Otavio R. Piske
Messaging Quality Assurance Engineer
