how to keep alive for connect via https, and to remove the warning of
automatically reconnect?
-----------------------------------------------------
following is my environment Description:
brokerURI on server side:
https://localhost:8015/broker?maximumConnections=1000amp;wireFormat.maxFrameSize=104857600
brokerURI on client side:
failover:(https://localhost:8015/broker)?maxReconnectDelay=10000&timeout=5000
log on client side:
2015-10-19 12:42:21,480 ActiveMQ InactivityMonitor Worker [WARN] Transport
(https://localhost:8015/broker) failed, attempting to automatically
reconnect
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too (>30000) long: https://localhost:8015/broker
        at
org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
2015-10-19 12:42:21,777 ActiveMQ Task-15 [INFO] Successfully reconnected to
https://localhost:8015/broker
2015-10-19 12:42:48,602 ActiveMQ InactivityMonitor Worker [WARN] Transport
(https://localhost:8015/broker) failed, attempting to automatically
reconnect
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too (>30000) long: https://localhost:8015/broker
        at
org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
2015-10-19 12:42:48,961 ActiveMQ Task-11 [INFO] Successfully reconnected to
https://localhost:8015/broker



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Broker-Protocol-is-http-or-https-InactivityIOException-on-client-side-tp4703106.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to