Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 23036 invoked from network); 12 Apr 2008 18:32:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Apr 2008 18:32:19 -0000 Received: (qmail 46138 invoked by uid 500); 12 Apr 2008 18:32:20 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 45796 invoked by uid 500); 12 Apr 2008 18:32:19 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 45787 invoked by uid 99); 12 Apr 2008 18:32:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Apr 2008 11:32:19 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of uma_rk@comcast.net designates 76.96.30.56 as permitted sender) Received: from [76.96.30.56] (HELO QMTA06.emeryville.ca.mail.comcast.net) (76.96.30.56) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Apr 2008 18:31:35 +0000 Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by QMTA06.emeryville.ca.mail.comcast.net with comcast id Ci181Z00M16AWCUA602i00; Sat, 12 Apr 2008 18:30:32 +0000 Received: from rmailcenter90.comcast.net ([204.127.197.190]) by OMTA06.emeryville.ca.mail.comcast.net with comcast id CiXm1Z00946xfYU8S00000; Sat, 12 Apr 2008 18:31:46 +0000 X-Authority-Analysis: v=1.0 c=1 a=AY85j3o5lyVde1T77Pq38Q==:17 a=pUR9InPapEDEXVz9Xe4A:9 a=pAD4hUtYKhE-hgelR-0A:7 a=TRTo1bQQut3efZfTfTF_XCQKeNgA:4 a=si9q_4b84H0A:10 a=c5zHXd76wwQA:10 Received: from [128.107.248.220] by rmailcenter90.comcast.net; Sat, 12 Apr 2008 18:31:46 +0000 From: uma_rk@comcast.net To: users@activemq.apache.org Subject: Re: AMQ4.1.1: Use of asyncDispatch Date: Sat, 12 Apr 2008 18:31:46 +0000 Message-Id: <041220081831.19012.4801001200005F3E00004A442206824693059DA10E039A@comcast.net> X-Mailer: AT&T Message Center Version 1 (Oct 30 2007) X-Authenticated-Sender: dW1hX3JrQGNvbWNhc3QubmV0 X-Virus-Checked: Checked by ClamAV on apache.org 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: > > uri="tcp://localhost:61616?wireFormat.maxInactivityDuration=0"/> > > > > > > > Peer B: > > uri="tcp://localhost:61616?wireFormat.maxInactivityDuration=0"/> > > > > > > > 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 >