Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type;
  b=CZcr+zEkjuu2Evv6ht7IsfIuJ2ZRke3zTmLET0SJWz00/csZgiumDiL7EjTzhop3OJwqrLAmcTtmqWv06pga1OaY9rYldMeC7TiiWZ2Pi0oCRMvspY0SDzQP4vnD6jtetkHeX76GL6iUKP7k4WA5v+9Mcn1HHLCUlDHF17q04to=;
Message-ID: <848822.22726.qm@web32404.mail.mud.yahoo.com>
Date: Tue, 7 Dec 2010 12:04:29 -0800 (PST)
From: Elizabeth Griffith <e_beth_82@yahoo.com>
Subject: JMS Dyname Ring Queues
To: users@qpid.apache.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1189219817-1291752269=:22726"

--0-1189219817-1291752269=:22726
Content-Type: text/plain; charset=us-ascii

I am upgrading my Java program from MRG 1.2 to MRG 1.3. I tried using the new 
addressing syntax to pick up the ability to create a dynamic queue as a ring 
queue. I made the queue non-durable with the auto-delete and exclusive flags. 
Before fail over, when I query the broker that I am going to fail over to, the 
dynamic ring queue appears on the queue list. However, when I fail over to it, 
the queue disappears. Most of the time JMS does not receive an exception that 
the queue does not exist so it does not know that it needs to recreate the 
queue. Therefore, it behaves as if it is connected, but it does not receive any 
messages. On rare occasions, an exception is received by JMS, which is passed on 
to my code. My code then recreates the queue. If I use the old syntax, the 
program fails over just fine. Is there something I might be missing in the 
addressing syntax that is preventing this from working correctly, or is there a 
race condition for JMS receiving an exception for the missing queue?

Thanks,

Liz


--0-1189219817-1291752269=:22726--