Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of Aleksi.Kallio@csc.fi designates
 193.166.3.97 as permitted sender)
Message-ID: <4F30E19E.6070808@csc.fi>
Date: Tue, 7 Feb 2012 10:32:30 +0200
From: Aleksi Kallio <aleksi.kallio@csc.fi>
Organization: CSC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.26) Gecko/20120130 Red Hat/3.1.18-1.el6_2 Thunderbird/3.1.18
MIME-Version: 1.0
To: "users@activemq.apache.org" <users@activemq.apache.org>
Subject: Re: How to create temporary topic without blocking?
References: <1328421360825-4358480.post@n4.nabble.com>
	 <4F2F9486.90307@csc.fi> <1328540789.11999.3.camel@OfficePC>
In-Reply-To: <1328540789.11999.3.camel@OfficePC>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit

Thanks! So there is no way to have both long and short timeouts in one 
connection?

I would like to keep the infinite failover, but then for certain API 
calls, have it fail immediately if connection is lost.


On 2012-02-06 17:06, Timothy Bish wrote:
> You need to use the Failover transport options to configure the
> transport to fail after some amount of time, the timeout option will let
> you do that, see:
>
> http://activemq.apache.org/failover-transport-reference.html
>
>
>
> On Mon, 2012-02-06 at 10:51 +0200, Aleksi Kallio wrote:
>> Hi,
>>
>> We have client apps connecting to our server environment using ActiveMQ,
>> with failover enabled. Our users can have the app open on a laptop while
>> moving from one network to another or to a completely unconnected place.
>>
>> ActiveMQ does beautiful failover, keeping the system running between
>> network connections. However there are certain cases when we would like
>> to use our own "failover mechanism".
>>
>> To do that, we would need to be able to check connection state or have
>> an exception thrown when connection is not active. Now when you try to
>> send a message and create a temporary reply topic without network
>> connection it hangs on session.createTemporaryTopic().
>>
>> How to not block on session.createTemporaryTopic() when the network is
>> disconnected?
>>
>> I tried setting useAsyncSend to true and checking
>> connection.isTransportFailed() before calling createTemporaryTopic(),
>> but neither of them helped.
>>
>> Creating a throwaway thread for the send attempt is a solution, but a
>> very crude one.
>>
>> All the best,
>> Aleksi
>>
>