On 06/07/2013 11:27 AM, Chris wrote:
Hi Timothy,
Thanks for your quick reply. I tried using stop(), but got the same
result... i appears the mutex gets deleted, and this result in the r6025
failure, since synchronisable object is an abstract class.
Are you aware of any other method to abort the start() at the moment? (a
workaround that would allow me to close() the connection later on)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-CPP-v3-7-0-how-to-close-a-connection-blocked-inside-a-start-when-using-failover-tp4667937p4668008.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Not sure, you'd have to look into the code, I can't remember if there is
any timeouts that apply to this case.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
www.camelone.org : The open source integration conference:
