activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jaya_srini <jya_sr...@Hotmail.com>
Subject Re: TransportListener question
Date Fri, 09 May 2008 15:28:20 GMT

given what I have said below, I am wondering if the following will work

The JMS client connects to the broker with the following conenction URI
(without async send parameter)

failover:(tcp://localhost:61616?wireFormat.maxInactivityDuration=-1)

In the code when I create the connection I set the async send to be true
using the setUseAsyncSend() API? Or will this parameter be ignored if the
transport is failover?


jaya_srini wrote:
> 
> Well, that's the problem. When we use jms.useAsyncSend in the connection
> URI with the failover transpoert we can't even start the JMS client. It
> hangs when it's trying to create the connection to the broker. We are
> using Active-MQ 5.0.0. These are the errors we see in the logs pertaining
> to ActiveMQ
> 
> *DEBUG 08:06:34.296,ActiveMQ
> Task,(org.apache.activemq.transport.failover.FailoverTransport:136)> 
> Connect fail to:
> tcp://localhost:61616?jms.useAsyncSend=true&wireFormat.maxInactivityDuration=-1,
> reason: java.lang.IllegalArgumentException: Invalid connect parameters:
> {jms.useAsyncSend=true}
> *DEBUG 08:06:34.296,ActiveMQ
> Task,(org.apache.activemq.transport.failover.FailoverTransport:152)> 
> Waiting 10 ms before attempting connection. 
> 
> which is what made me think that useAsyncSend is not possible to use with
> failover. If I remove the failover transport client is able to connect
> successfully but then we lose the features we wanted with failover.
> 
> The connection URI looks like this
> 
> failover:(tcp://localhost:61616?jms.useAsyncSend=true&wireFormat.maxInactivityDuration=-1)
> 
> thanks
> jaya
> 
> James.Strachan wrote:
>> 
>> 2008/5/9 jaya_srini <jya_srini@hotmail.com>:
>>>
>>>  Thanks so much for the responses. Can you tell me how I can use Async
>>> Sends
>>>  with the Failover transport? I tried the jms.useAsyncSend parameter in
>>> the
>>>  connection URI but that just causes the client to hang.
>> 
>> Was the client connected to the broker at the time? The restriction
>> with all transports is the client must be connected to a broker to
>> create connections / sessions / producers / consumers.
>> 
>> -- 
>> James
>> -------
>> http://macstrac.blogspot.com/
>> 
>> Open Source Integration
>> http://open.iona.com
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/TransportListener-question-tp17142309s2354p17150502.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message