On Sat, 2012-04-07 at 13:01 -0600, Chris Robison wrote:
> Sorry, that was really badly written. Is the .NET client library supposed
> to be able to reconnect itself with the ActiveMQ broker or is that
> something I have to catch and do myself?
in order to have the client handle connection errors
Sorry, that was really badly written. Is the .NET client library supposed
to be able to reconnect itself with the ActiveMQ broker or is that
something I have to catch and do myself?
On Sat, Apr 7, 2012 at 1:00 PM, Chris Robison wrote:
> Is the .NET client library reconnect itself so is that somet
Is the .NET client library reconnect itself so is that something I have to
catch and do?
On Sat, Apr 7, 2012 at 12:37 PM, Chris Robison wrote:
> I'm assuming you mean set it on the connection factory. I've tried that,
> but no go. The only way I've found to recover from this is to delete the
> Ka
I'm assuming you mean set it on the connection factory. I've tried that,
but no go. The only way I've found to recover from this is to delete the
KahaDB on the activemq server and restart all services.
On Sat, Apr 7, 2012 at 11:59 AM, Timothy Bish wrote:
> On Sat, 2012-04-07 at 11:56 -0600, Chri
On Sat, 2012-04-07 at 11:56 -0600, Chris Robison wrote:
> I'm running into an interesting issue. I have a client connecting to an
> activemq server, trying to consume messages and reply to a temporary
> destination set. The ActiveMQ server debug is showing the following:
>
> 2012-04-07 13:20:25,7
