-
Bug
-
Resolution: Done
-
Major
-
None
-
AMQ 7.1.0.GA
-
None
-
Release Notes, User Experience
-
-
-
Documented as Resolved Issue
-
-
AMQ Broker 1833, AMQ Broker 1836
Implemeting the class org.apache.activemq.artemis.protocol.amqp.broker.AmqpInterceptor the intercept method receives a null reference to the RemotingConnection.
The customer needs this information to log the remote address into their logs file. Please, see a reproducer in the link bellow:
http://pastebin.test.redhat.com/594102
The outcome of this interceptor is:
IN:
2018-05-21 17:55:47,295 INFO [amq.sample.interceptor.CustomLogInterceptor] Packet: org.apache.activemq.artemis.protocol.amqp.broker.AMQPMessage "type":"in", "message-id":"0", "correlation-id":"null", "destination":"Queue::Test", "payload":"Text!", "clientID":"null-client-id", "remoteAddress":"null-remote-address", "protocolName":"null-protocol-name", "amqRouteTo":"null"
OUT:
2018-05-21 17:58:25,241 INFO [amq.sample.interceptor.CustomLogInterceptor] Packet: org.apache.activemq.artemis.protocol.amqp.broker.AMQPMessage "type":"out", "message-id":"139", "correlation-id":"null", "destination":"Queue::Test", "payload":"Text!", "clientID":"null-client-id", "remoteAddress":"null-remote-address", "protocolName":"null-protocol-name", "amqRouteTo":"null"