Justin,
Good point. That’s what I am wondering is why is it listening on an IPv6
address. I will check on that.
Thank you.
From: Justin Bertram
Date: Monday, June 2, 2025 at 12:04 PM
To: users@activemq.apache.org
Subject: Re:
org.apache.activemq.artemis.spi.core.protocol.RemotingConnection
I've not seen this specific behavior before. I'm not sure why it would do
that.
To be clear,
org.apache.activemq.artemis.spi.core.protocol.RemotingConnection#getRemoteAddress
is basically just a wrapper around io.netty.channel.Channel#remoteAddress
[1] so the exact behavior here will be determined
Is there any reason why the following code would return the IPv6 loopback
address and not the actual physical IPv4 address of the client?
import io.netty.handler.codec.mqtt.MqttMessage;
import org.apache.activemq.artemis.core.protocol.mqtt.MQTTInterceptor;
import org.apache.activemq.artemis.spi.c
