activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes" <e.se...@gmail.com>
Subject Re: AMQ4.1.1: Use of asyncDispatch
Date Mon, 14 Apr 2008 19:43:50 GMT
I can maybe help with the command-line parameter:  try using
jms.asyncDispatch=true.  On NMS (the .NET client), you would use
connection.asyncDispatch=true.


On Sat, Apr 12, 2008 at 11:31 AM, <uma_rk@comcast.net> wrote:

>
>
> I would like to use asyncDispatch to solve this problem.
> When I try to create a ConnectionFactory using
> the URL (in Spring configuration, if that matters at all):
>
>   brokerURL:="tcp://localhost:61616?asyncDispatch=true"
>
> I get invalid connection parameter exception.
>
> The brokerURL
>
>        tcp://localhost:61616?broker.asyncDispatch=true"
>
> yields the same result.
>
> What is the correct way to opt for asyncDispatch when creating a
> connection factory using Spring configuration?
>
> Also, what is the difference between asyncDispatch and asyncSend?
>
> Regards
>
> /Ur
>  -------------- Original message ----------------------
> From: uma_rk@comcast.net
> >
> > I am using ActiveMQ 4.1.1 with a very simple peer to peer
> > connection. I find that after a few exchanges, the messages
> > from A to B stall - the clients of A seem to hang while sending
> > a message (FWIW, only TextMessages are used):
> >
> >   Peer A:
> >        <transportConnectors>
> >        <transportConnector  name="openwire"
> >
> uri="tcp://localhost:61616?wireFormat.maxInactivityDuration=0"/>
> >     </transportConnectors>
> >
> >     <networkConnectors>
> >         <networkConnector name="remote-broker"
> uri="static://(tcp://B:61616)" />
> >     </networkConnectors>
> >
> > Peer B:
> >        <transportConnectors>
> >        <transportConnector  name="openwire"
> >
> uri="tcp://localhost:61616?wireFormat.maxInactivityDuration=0"/>
> >     </transportConnectors>
> >
> >     <networkConnectors>
> >         <networkConnector name="remote-broker"
> uri="static://(tcp://A:61616)" />
> >     </networkConnectors>
> >
> > I would ike to understand what could be causing this problem.
> > At the smetime I want to enable asyncDispatch.
> >
> > When the URL syntax
> >
> >      tcp://localhost:61616?asyncSend=true
> >
> > is rejected as "bad connetion parameter". The same result with
> >
> >     tcp://localhost:61616?broker.asyncSend=true
> >
> >
> > Please help!
> >
> > Regards
> >
> > /Ur
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message