Hello, Is it possible to change some of the default settings used when a queue is created, note I do not mean override them at runtime?
So currently if a queue is created the default policy when the queue size is exceeded is to block the producer so no more data arrives. This is not acceptable in my system. I would like all queues that are created to be created with the default policy_type of RING, so the producer is never blocked. However all my queues are created dynamically by the consumers using the AMQP syntax, ideally I would prefer not to rely on the consumers to create the queues with a RING policy. So what I would like is for all queues to be created at runtime to use a RING policy, without having to over-ride it at runtime. Can I change the default policy to be RING? Thanks Richard -----Original Message----- From: Steve Huston [mailto:[email protected]] Sent: 01 April 2011 18:49 To: [email protected] Subject: RE: Qpid Federation What version(s) of Qpid and what platforms is this on? -- Steve Huston, Riverace Corporation Total Lifecycle Support for Your Networked Applications http://www.riverace.com > -----Original Message----- > From: Fallon, Richard [mailto:[email protected]] > Sent: Friday, April 01, 2011 12:08 PM > To: [email protected] > Subject: Qpid Federation > > > > Hello, > > I am running 2xQpid brokers on 2 different boxes across a number of > network hops, called SRC_BROKER and DEST_BROKER. > > I am running a federated topology whereby the brokers are connected > via a durable dynamic route to the default topic exchange 'amq.topic' > by running the command > > qpid-route -d add dynamic add DEST_BROKER SRC_BROKER amq.topic > > The SRC_BROKER is receiving data to the amq.topic exchange and, via > the dynamic route, the DEST_BROKER receives that same data . > > ===== ====== > | SRC| <----dynamic route----> | DEST | > ===== ====== > > > I have subscribers to the DEST_BROKER happily reading messages. > > The SRC_BROKER shows it has a conection established with the > DEST_BROKER and there is a queue created on the SRC_BROKER. > I understand that the dynamic route creation has created that queue on > the SRC_BROKER broker and the DEST_BROKER is receiving its messages > from that provate queue. > > Most of the time this works perfectly well. > > But occasionally the data stops being received at the DEST_BROKER. > Closer investigation shows the connection is still active on the > SRC_BROKER to the DEST_BROKER but the private queue has gone. The > SRC_BROKER is still functioning and receiving messages, the > DEST_BROKER is still functioning and capable of receiving messages, > just NOT from the dynamic route. > > If I re-run the command to add the dyanmic route > > qpid-route -d add dynamic add DEST_BROKER SRC_BROKER amq.topic > > The data starts to flow again. > > I have been monitoring this for days and am unable to find any useful > info in the logs and the queues and connections all look fine. > > I have no idea what is causing the queue on the SRC_BROKER to > disappear. > > If there was a network failure would this cause the deletion of the > private queue on the SRC_BROKER? > > How do I ensure that my durable dynamic route remains? Am I missing > something. > > Thanks in advance > > Richard > > > _______________________________________________________ > Atos Origin and Atos Consulting are trading names used by the Atos > Origin group. The following trading entities are registered in > England and Wales: Atos Origin IT Services UK Limited (registered > number 01245534) and Atos Consulting Limited (registered number > 04312380). The registered office for each is at 4 Triton Square, > Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983 > > This e-mail and the documents attached are confidential and intended > solely for the addressee, and may contain confidential or privileged > information. If you receive this e-mail in error, you are not > authorised to copy, disclose, use or retain it. Please notify the > sender immediately and > delete this email from your systems. As emails may be > intercepted, amended or lost, they are not secure. Atos Origin > therefore can accept no liability for any errors or their content. > Although Atos Origin endeavours to maintain a virus-free network, we > do not warrant that this transmission is virus-free and can accept no > liability for any damages > resulting from any virus transmitted. The risks are deemed > to be accepted by everyone who communicates with Atos Origin by email. > _______________________________________________________ > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected] _______________________________________________________ Atos Origin and Atos Consulting are trading names used by the Atos Origin group. The following trading entities are registered in England and Wales: Atos Origin IT Services UK Limited (registered number 01245534) and Atos Consulting Limited (registered number 04312380). The registered office for each is at 4 Triton Square, Regents Place, London, NW1 3HG.The VAT No. for each is: GB232327983 This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos Origin therefore can accept no liability for any errors or their content. Although Atos Origin endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos Origin by email. _______________________________________________________ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
