mq.apache.org
> Subject: Re: "WARNING: Transport failed" ...
> org.apache.activemq.transport.failover.FailoverTransport
> handleTransportFailure
>
> Is this timeout the same as the:
>
> soTimeout (long) sets the SO_TIMEOUT value (in milliseconds) on the socket
>
an be specified on
a JMS solution.
Thanks,
Eric
Andrew wrote:
That's all it was. Thanks.
-Original Message-
From: James Strachan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2008 1:06 AM
To: users@activemq.apache.org
Subject: Re: "WARNING: T
That's all it was. Thanks.
-Original Message-
From: James Strachan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2008 1:06 AM
To: users@activemq.apache.org
Subject: Re: "WARNING: Transport failed" ...
org.apache.activemq.transport.failover.FailoverTransport
handleT
Note that failover reconnected fine BTW
On 04/03/2008, James Strachan <[EMAIL PROTECTED]> wrote:
> It looks like the socket failed - could be thebroker thinking the
> socket was inactive. You could try increasing or disabling the
> inactivity timeout.
>
>
> On 03/03/2008, Andrew <[EMAIL PROTECT
It looks like the socket failed - could be thebroker thinking the
socket was inactive. You could try increasing or disabling the
inactivity timeout.
On 03/03/2008, Andrew <[EMAIL PROTECTED]> wrote:
> Anyone know why this would happen? Other clients connected simultaneously
> don't disconnect. E
Anyone know why this would happen? Other clients connected simultaneously
don't disconnect. Everything is on a simple LAN so no networking issues
should exist for one client and not others..
Thanks,
Andrew
Mar 3, 2008 3:00:55 PM
org.apache.activemq.transport.failover.FailoverTransport
handleTr
