Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 7373 invoked from network); 21 May 2009 09:03:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 May 2009 09:03:58 -0000 Received: (qmail 55610 invoked by uid 500); 21 May 2009 09:04:11 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 55576 invoked by uid 500); 21 May 2009 09:04:11 -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 55566 invoked by uid 99); 21 May 2009 09:04:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2009 09:04:11 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [192.77.186.17] (HELO mx3.progress.com) (192.77.186.17) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2009 09:04:01 +0000 Received: from mx3.progress.com (127.0.0.1) by mx3.progress.com (MlfMTA v3.2r9) id h2kcg20171s2 for ; Thu, 21 May 2009 05:03:40 -0400 (envelope-from ) Received: from progress.com ([192.233.92.16]) by mx3.progress.com (SonicWALL 6.2.2.1073) with ESMTP; Thu, 21 May 2009 05:03:16 -0400 Received: from NTEXFE02.bedford.progress.com (ntexfe02 [10.128.10.26]) by progress.com (8.13.8/8.13.8) with ESMTP id n4L92w2v027574 for ; Thu, 21 May 2009 05:02:58 -0400 (EDT) Received: from MAIL02.bedford.progress.com ([172.16.2.55]) by NTEXFE02.bedford.progress.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 21 May 2009 05:02:58 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9D9F2.EF8E3FC2" Subject: Observations from Master Slave setup Date: Thu, 21 May 2009 05:02:56 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Observations from Master Slave setup Thread-Index: AcnYb+EPq9toZ8xtReWoxD0k1zK3rQBgs/cg From: "Nawaz Ahmed" To: X-OriginalArrivalTime: 21 May 2009 09:02:58.0747 (UTC) FILETIME=[EFEE88B0:01C9D9F2] X-Mlf-Version: 6.2.2.1073 X-Mlf-UniqueId: o200905210902580259620 X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C9D9F2.EF8E3FC2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi , =20 I was trying to configure a pure master slave configuration with Fuse Message broker 5.3.0.1 . First I tried without security. I created two brokers in different machines. The transport connectors looked like this: =20 =20 This configuration worked fine. =20 After this I tried with security. =20 I gave master brokers transport connector as . Then I configured a simple authentication plugin as follows. =20 =20 After doing this the master broker didn't start. I threw security exception that passwords don't match. But when I changed the transport connector to = it started fine.=20 =20 After this the slave broker in another machine could not connect to the master. It threw connection refused exception. But when I configured the slave in the same machine as master with different port numbers for transport connectors it successfully attached itself with the master. =20 Finally I removed the discoveryUri=3D"multicast://default" from the transport connectors. Then everything worked fine. The master slave got working in two different machines with machine names in their transport connectors URI. =20 >From the following observations I have a few questions: =20 1. Why the broker throws a security exception of User name or password is invalid if I use the following transport connector. . 2. Why the exception vanishes if I use localhost instead of machine name. 3. Even if the master starts with localhost the slave in other machine gets connection refused exception. 4. When I remove the discovery URI from the transport connectors everything works fine. =20 Any suggestions on this will be appreciated. =20 Regards, Nawaz Ahmed =20 ------_=_NextPart_001_01C9D9F2.EF8E3FC2--