On Thu, 2011-10-20 at 17:34 -0500, qt4x11 wrote:
> We are trying to instantiate a new ActiveMQConnectionFactory in our code
> using the brokerURL
>
> failover:(ssl://107.22.0.25:61616,ssl://174.129.78.76:61616
> )?tcp.keepAlive=true
>
Try this:
failover:(ssl://107.22.0.25:61616?keepAlive=true,ssl://174.129.78.76:61616?keepAlive=true)
Transport options go on the specific transport, keepAlive is not a
property of the failover transport. Tcp KeepAlive isn't really all that
helpful though as it only checks every two hours or so for a connection
by default. The InactivityMonitor will be sending its own keep alive
commands between broker and client which should be all you need.
> This does not work. We get a stack trace during application deployment
>
> 14:47:19,203 ERROR [stderr] (MSC service thread 1-1) Caused by:
> java.lang.IllegalArgumentException: Invalid connect parameters:
> {tcp.keepAlive=true}
> 14:47:19,203 ERROR [stderr] (MSC service thread 1-1) at
> org.apache.activemq.transport.failover.FailoverTransportFactory.createTransport(FailoverTransportFactory.java:64)
> 14:47:19,203 ERROR [stderr] (MSC service thread 1-1) at
> org.apache.activemq.transport.failover.FailoverTransportFactory.doConnect(FailoverTransportFactory.java:37)
> 14:47:19,203 ERROR [stderr] (MSC service thread 1-1) at
> org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:51)
> 14:47:19,203 ERROR [stderr] (MSC service thread 1-1) at
> org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:80)
> 14:47:19,203 ERROR [stderr] (MSC service thread 1-1) at
> org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:243)
> 14:47:19,203 ERROR [stderr] (MSC service thread 1-1) ... 30 more
>
>
> If we remove options from the brokerURL
>
> failover:(ssl://107.22.0.25:61616,ssl://174.129.78.76:61616)
>
> we're able to deploy successfully.
>
> We are using ActiveMQ 5.5.0. What is it about the keepAlive option we're
> appending to the failover brokerURL that is causing deployment errors? Is
> there any way we can use tcp keepAlive with failover?
>
> Thanks.
--
Tim Bish
------------
FuseSource
Email: tim.b...@fusesource.com
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/
