You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by christine1 <ch...@gmail.com> on 2013/02/18 22:00:33 UTC
Connection.close() delay with failover and CMS
When I close a Connection in CMS (C++) I get a 2 second delay only if I'm
using a failover protocol. This doesn't happen in Java or if I'm not using
a failover protocol. Has anyone else experienced this? Is there an option
that I can set to prevent this? I'm using ActiveMQ-CPP 3.4.4 with Linux.
Thanks!
--
View this message in context: http://activemq.2283324.n4.nabble.com/Connection-close-delay-with-failover-and-CMS-tp4663637.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Connection.close() delay with failover and CMS
Posted by Timothy Bish <ta...@gmail.com>.
On 02/18/2013 04:00 PM, christine1 wrote:
> When I close a Connection in CMS (C++) I get a 2 second delay only if I'm
> using a failover protocol. This doesn't happen in Java or if I'm not using
> a failover protocol. Has anyone else experienced this? Is there an option
> that I can set to prevent this? I'm using ActiveMQ-CPP 3.4.4 with Linux.
> Thanks!
This will be fixed in the v3.6.0 release, currently it can't be back
ported to the earlier code as it need some changes that break ABI.
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Connection-close-delay-with-failover-and-CMS-tp4663637.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/