Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 17760 invoked from network); 13 Dec 2010 23:30:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Dec 2010 23:30:59 -0000 Received: (qmail 40955 invoked by uid 500); 13 Dec 2010 23:30:59 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 40931 invoked by uid 500); 13 Dec 2010 23:30:59 -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 40922 invoked by uid 99); 13 Dec 2010 23:30:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Dec 2010 23:30:59 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tabish121@gmail.com designates 209.85.216.43 as permitted sender) Received: from [209.85.216.43] (HELO mail-qw0-f43.google.com) (209.85.216.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Dec 2010 23:30:51 +0000 Received: by qwk3 with SMTP id 3so37639qwk.2 for ; Mon, 13 Dec 2010 15:30:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:in-reply-to :references:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=cH46uZg36fmhtnVbj69Qm8TfsuidpBBKYWgsyyoy1Tk=; b=mYSh0DXsFRxJJ05lQKYpIwWverUICmX/N/FRDySdFOlZehPemV0lDw4Tudj1UdIJsl 2HemRRFUZ/cXDO7FsUfBhtYXyl6r/C6/KhZXtISq1H6g8qoV166MpQdnhnezAbgMIaq7 rMyXybvJ/DkxOYaL3VKcBe3j3rabXRCvEVGps= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=rV6nB6p5OTOaigvMaAT6Pw/RfSLtZAN/a2S58XTF55GCtZv16JTBCB+kj8eLe4xj6n IggenJkMnLV46ZYVkDxYW4DpyEIk7LMAfKBotQ8jALOYqCRaIPB6mF9YA4aGHxKxhamr Cl9AEdC0GTGifXZ1QW029JL75KwGtG6wmgKfA= Received: by 10.224.53.194 with SMTP id n2mr2990146qag.367.1292283029969; Mon, 13 Dec 2010 15:30:29 -0800 (PST) Received: from [192.168.2.150] (c-69-143-50-138.hsd1.va.comcast.net [69.143.50.138]) by mx.google.com with ESMTPS id q12sm1029604qcu.42.2010.12.13.15.30.28 (version=SSLv3 cipher=RC4-MD5); Mon, 13 Dec 2010 15:30:29 -0800 (PST) Subject: Re: Using SonicMQ client with ActiveMQ server? From: Timothy Bish To: users@activemq.apache.org In-Reply-To: <1292281406363-3086206.post@n4.nabble.com> References: <1292281406363-3086206.post@n4.nabble.com> Content-Type: text/plain; charset="UTF-8" Date: Mon, 13 Dec 2010 18:30:27 -0500 Message-ID: <1292283027.2438.1.camel@office> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 (2.30.3-1.fc13) Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Mon, 2010-12-13 at 15:03 -0800, digant wrote: > Hello, > > We have some old code that uses the SonicMQ libraries and we're trying to > move them to ActiveMQ server. So far, when they try to negotiate a > connection, I get: > > Transport failed: java.io.IOException: Remote wire format magic is invalid > > I see that ActiveMQ is sending: > > Sending: WireFormatInfo { version=3, properties={TightEncodingEnabled=true, > CacheSize=1024, TcpNoDelayEnabled=true, SizePrefixDisabled=false, > StackTraceEnabled=true, MaxInactivityDurationInitalDelay=10000, > MaxInactivityDuration=30000, CacheEnabled=true}, magic=[A,c,t,i,v,e,M,Q]} > > And it is receiving: > > Received WireFormat: WireFormatInfo { version=0, properties={}, > magic=[,,,,,,,]} > > Any ideas of how I can change/fix this, or even what the root of the problem > is? can I get ActiveMQ to accept version 0? (the default wireformat should > be 0, from my readings). And it shouldn't care about the magic, I didn't > think. ActiveMQ and SonicMQ use two entirely different wire protocols so you can't just point your SonicMQ client at an ActiveMQ broker. You'd need to either use a JMS to JMS bridge, or if the client is using pure JMS API calls then just have your client use the ActiveMQ Java client instead. Regards -- Tim Bish ------------ FuseSource Email: tim.bish@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/