Hello,
I've got a very similar problem with ActiveMQ 5.12.0 when building a broker
network via a SSL connector. I have set
networkConnector
uri="static:(failover:(ssl://${offboardBroker1}:10017?wireFormat.maxInactivityDuration=0,ssl://${offboardBroker2}:10017?wireFormat.maxInactivityDuration=0)?randomize=true)"
...
in the network connector definition. However, after startup an exception
(java.io.EOFexception at
java.io.DataInputStream.readInt(DataInputStream.java:392) is thrown, and the
broker on the other side logs that the network connection has been
interrupted due to inactivity although the maxInactivityDuration was set to
zero, and the monitor should therefore be activated.
The connection is re-established, but after that the consumers of my broker
cannot be seen on the other side any longer.
With ActiveMQ 5.11.1, the setting maxInactivityDuration=0 worked, and the
connection is never timed out. Seems to be different in 5.12.0.
Of course, I would also be interested if anybody has an idea why my
consumers are no longer seen on the broker connected via the network
connector after a reconnection. With "normal" network disruption, this
works, but after the exception, it doesn't.
Best Regards,
Jochen
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-org-apache-activemq-transport-InactivityIOException-Channel-was-inactive-for-too-30000-long-6-tp4702833p4703169.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
