bject: Re: Amq client crash when losing connection to broker
tabish121 wrote:
Please upgrade to ActiveMQ-CPP 2.1.1 as this sounds like an
error that
we fixed. Then let us know if it still misbehaves.
Regards
Tim
Still doesnt work.
I should mention though, th
close
>> part, stop() will work though. Each queue runs in a seperate
>> thread with their own activemq session/connection/.. objects.
>>
>> By the way, if i open some queue with a wrong (unknown) host,
>> e.getMessage().c_str() returns "Success".
>>
>>
tivemq.apache.org
> Subject: Re: Amq client crash when losing connection to broker
>
>
>
> tabish121 wrote:
> >
> > Please upgrade to ActiveMQ-CPP 2.1.1 as this sounds like an
> error that
> > we fixed. Then let us know if it still misbehaves.
> >
& e)
{
e.getMessage().c_str()
}
--
View this message in context:
http://www.nabble.com/Amq-client-crash-when-losing-connection-to-broker-tf4792112s2354.html#a13726015
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Please upgrade to ActiveMQ-CPP 2.1.1 as this sounds like an error that
we fixed. Then let us know if it still misbehaves.
Regards
Tim
On Mon, 2007-11-12 at 08:19 -0800, pfid wrote:
> I'm using ActiveMQ-CPP 2.1 in my client application, and the broker version
> 4.1.1.
>
> in case the client lose
however, since
1) i would like to close the connection immediately once i notice the
exception, not after the first try to write this broken connection fails
2) i have read-mode connections as well, i can't write on those
could someone help me on this?
--
View this message in context:
http://www.nabble.com/Amq-client-crash-when-losing-connection-to-broker-tf4792112s2354.html#a13708604
Sent from the ActiveMQ - User mailing list archive at Nabble.com.