You might have some luck trying the "keepAlive" option detailed here:
http://activemq.apache.org/tcp-transport-reference if the connection is
getting terminated by the haproxy for some reason.
Br,
Anton
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
You're right, I re-read the log and you did provide the broker logs. Sorry
for the confusion.
I assume the client logs show something similar for the root cause (even
though it'll be a different stack trace)?
Unfortunately I don't have any experience configuring or troubleshooting
HAProxy. I reco
No. The connection established using localhost is working as expected.
The question is how to configure HAProxy properly? I just used the old
configuration working with Activemq 5.15.3
The broker log is the one I have already posted, isn't it? Is there another
specific log?If yes I do not know how
I hadn't understood that the connection was initially successful and data
passes correctly at first, so thank you for clarifying that.
Do you see the same behavior if you connect directly to the broker without
going through the HAProxy? Might this be introduced by the loan balancer,
possibly due t
Sorry but iI do not understand what you mean.
The clients regularly estabilish the connection, subscribe and publish. But
after some seconds they are disconnected and I found a lot af Connection
reset server/broker side.
I use the same configuration fo years, but with an older Activemq version.
I'
What URI (without the HAProxy IP, of course) are you using in your MQTT
client? It's OK/expected that the underlying protocol be TCP at the network
level, but the client needs to be specifying mqtt:// in the URI to tell the
client library to use MQTT over TCP instead of OpenWire over TCP. It also
n
I forgot to write that Activemq is behind HAProxy as pfsense plugin.
The client MQTT connects to the the public pfsense WAN->nat to VIP -> VIP is
HAProxy frontend -> backend with one server.
HAproxy frontend is set as tcp. ActiveMQ listen on:
--
Sent from: htt
>From the logs, it looks like the URI used for your connection is using
tcp:// as the transport protocol, whereas an MQTT connection use mqtt://.
And is the port you're connecting to running the MQTT protocol, or is it an
OpenWire port?
Tim
On Mon, Apr 20, 2020, 10:02 AM JJ wrote:
> Simple MQTT
Simple MQTT connection produce continously errors, and after few seconds
client disconnection.
activemq.xml is the default one.
Any help/hint?
java.net.SocketException: Connection reset
at
java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)[:]
at
java.base/ja
