Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 18744 invoked from network); 23 Apr 2010 22:34:32 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Apr 2010 22:34:32 -0000 Received: (qmail 61327 invoked by uid 500); 23 Apr 2010 22:34:32 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 61297 invoked by uid 500); 23 Apr 2010 22:34:32 -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 61289 invoked by uid 99); 23 Apr 2010 22:34:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Apr 2010 22:34:32 +0000 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=FREEMAIL_FROM,HTML_FONT_FACE_BAD,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tammer.salem@googlemail.com designates 72.14.220.156 as permitted sender) Received: from [72.14.220.156] (HELO fg-out-1718.google.com) (72.14.220.156) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Apr 2010 22:34:25 +0000 Received: by fg-out-1718.google.com with SMTP id l26so477460fgb.14 for ; Fri, 23 Apr 2010 15:34:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=cV4uIFpF11P9OxHYOLeCHnpNo/mBEMX/lnNJnrJGeGw=; b=wuDp1bIj9ssGyUOJazdJa6qES2a+lsLEWJd3Mr+kL70OG37E0jTrI/hnIBBp08s7wj UFgLNZvbeQAX/mjPU04Lm+vSPiTswNQJ61M0qGxT+Pt/gyW1vPX7M4ABjVwHoRvGfViE tgVB2/hyYbMeTvpLRW7kDsAV4n1YTlOLnTtDs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=X2veC/Ly9SIg31YB65MalPf97bwsKUSQWZQ4mBqylnxRbW8JdT72dFoEjdS4mv6h/0 uk6Adf3ZiIydFr7zYHIHIyhUlKd7x5jFM9OELs1iI3AQm9xfxhVzOH18wnqibUmoloKz tVmql4jS34qTW0BcxZI/2oVyMu0GbSdN95hN4= MIME-Version: 1.0 Received: by 10.239.182.210 with SMTP id r18mr63339hbg.54.1272062044631; Fri, 23 Apr 2010 15:34:04 -0700 (PDT) Received: by 10.239.178.135 with HTTP; Fri, 23 Apr 2010 15:34:04 -0700 (PDT) In-Reply-To: References: Date: Fri, 23 Apr 2010 23:34:04 +0100 Message-ID: Subject: Re: AMQ integration with JBoss - Failover to TCP when trying to use VM protocol From: Tammer Salem To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=00163649a1a54d75840484ef06c2 X-Virus-Checked: Checked by ClamAV on apache.org --00163649a1a54d75840484ef06c2 Content-Type: text/plain; charset=ISO-8859-1 I am still having a problem of AMQ going to TCP/IP connectivity on fail-over even though I have VM protocol enabled. Has anyone seen this happen? On 14 April 2010 20:29, Tammer Salem wrote: > That is the config I have. > So this is the line from my ra.xml: > > > > > > The URL to the ActiveMQ server that you want this connection >> to connect to. If using > > an embedded broker, this value should be 'vm://localhost'. > > > > ServerUrl > > java.lang.String > > vm://localhost > > > > > Both my connection factories for the queue and topic data sources both > point to the vm implementation: > > > > activemq/QueueConnectionFactory > > > > > > activemq-ra.rar > > >> javax.jms.QueueConnectionFactory > > vm://localhost > > > > 1 > > 200 > > 30000 > > 3 > > > > >> > > activemq/TopicConnectionFactory > > > > > > activemq-ra.rar > > >> javax.jms.TopicConnectionFactory > > vm://localhost > > > > 1 > > 200 > > 30000 > > 3 > > > > > and when I actually send a message I get this line in my log: > > INFO [FailoverTransport] Successfully connected to tcp://localhost:61616 > > > > Anyone have any idea where else I could look? > > regards, > Tammer > > > On 13 April 2010 09:55, Gary Tully wrote: > >> The vm transport is enabled by default on the broker. To use it from the >> RAR, you just need to use 'vm://localhost' in the ServerUrl config >> property >> in the ra.xml or override it via the appserver config. >> >> On 12 April 2010 23:31, Tammer Salem wrote: >> >> > Hello All, >> > I'm having some problems with my AMQ/JBoss integration. I've followed >> the >> > guide as specified on the site: >> > http://activemq.apache.org/integrating-apache-activemq-with-jboss.html >> > >> > Everything works fine - except when I've come to fire a message (from >> > within >> > JBoss) I expect it to use the vm:// protocol. Instead I get a failover >> > message and it tells me that it's using TCP instead. >> > First off it's great that it can recover from this and still actually >> send >> > out a message, but I feel like communicating over TCP/IP within the same >> VM >> > is a bit silly. >> > >> > My question here is if I've defined the vm:// protocol in the ra.xml and >> my >> > data source file, does it also need to be configured in the >> > broker-config.xml as a separate broker? >> > >> > regards, >> > Tammer >> > >> >> >> >> -- >> http://blog.garytully.com >> >> Open Source Integration >> http://fusesource.com >> > > --00163649a1a54d75840484ef06c2--