that is an interesting use case. A combination of the failover: transport that only reconnects on demand and an inactivity timeout that does not use keepAlives could do it. When there is no activity, the connection can timeout, that is possible on trunk with the useKeepAlive=false attribute, having the failover transport only reconnect on demand may need some code changes as it typically tries to reconnect after some timeout. You could make that reconnect delay very large I guess.
On 26 May 2010 09:49, gondor771 <t...@mips.com.hr> wrote: > > Hi, > > I am using "forwarding bridge" in many-to-one configuration. Many ActiveMQ > clients (just plain ActiveMQ local server acting as a buffer) will be > forwarding several queues defined with staticallyIncludedDestinations to > central (remote) ActiveMQ. So far, experiments confirm that all is working > fine. > > However there is one problem with forwarding bridge - it keeps TCP/IP > connection all the time. As there could be really many ActiveMQ clients => > that will kill network router with overload of active TCP/IP connections. > > Most of these ActiveMQ clients will be idle 99% of the time (no data in > queues to forward). > > Is there a way to configure client ActiveMQ in forwarding bridge mode to > connect to remote server ONLY when there is something to be sent (and > disconnect when done, eg queue empty) ? > > Can that be done by configuration or the only option is coding an > application ? > > PS. Google did not help me on this one.:-( > > Tom > -- > View this message in context: > http://old.nabble.com/Forwarding-bridge---connect-at-need-feature---tp28678019p28678019.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
