Broker URL - Connection Options
Hi, Guru Could you please clarify the following. It was some settings in qpid v0.7: retries connecttimeout connectdelay http://qpid.apache.org/books/0.7/Qpid-Book/html/ch11.html#BindingURLFormat They are still in code, but there is no any info in latest docs. Does this settings work in qpid version 0.12? If no, what should I use to implement reconnect behavior? Reragds, Boris ___ The information contained in this message may be privileged and conf idential and protected from disclosure. If you are not the original intended recipient, you are hereby notified that any review, retransmission, dissemination, or other use of, or taking of any action in reliance upon, this information is prohibited. If you have received this communication in error, please notify the sender immediately by replying to this message and delete it from your computer. Thank you for your cooperation. Troika Dialog, Russia. If you need assistance please contact our Contact Center (+7495) 258 0500 or go to www.troika.ru/eng/Contacts/system.wbp - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
Alternate Exchange of Alternate Exchange
Hi all, I have a three exchanges. Let's say E1, E2, E3 where E2 is alternate exchange of E1 and E3 is alternate exchange of E2. If a message can not be routed to E1, then it should go to E2. This works. But if it can not be routed to E2 it should go to E3, but it does not. Is this intended behaviour? Thanks and regards, Tomas - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
Re: Alternate Exchange of Alternate Exchange
On 11/16/2011 12:16 PM, Tomáš Šoltys wrote:
Hi all,
I have a three exchanges. Let's say E1, E2, E3 where E2 is alternate
exchange of E1 and E3 is alternate exchange of E2.
If a message can not be routed to E1, then it should go to E2. This
works. But if it can not be routed to E2 it should go to E3, but it
does not.
Is this intended behaviour?
The AMQP 0-10 specification has a rule ('double-failure' on p216), that
states:
A message which is being routed to a alternate exchange,
MUST NOT be re-routed to a secondary alternate exchange
if it fails to route in the primary alternate exchange.
After such a failure, the message MUST be dropped. This
prevents looping.
Any other behaviour would be a deviation from the specification (and of
course would need to include detection of loops, at which point message
would presumably be dropped).
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
AMQP 0-9-1
Hi All, How can I to setup qpidd (cpp) to speak AMQP 0-9-1 ? We are using QPID qpid-cpp-server-0.10-2.fc14 and rabbitmq java client 2.0.0 Regards Henry Molina P Considere el medioambiente antes de imprimir este correo La información contenida en este mensaje y en sus documentos adjuntos, es estrictamente confidencial y privado para sus destinatarios. Cualquier uso, reproducción, divulgacion o distribucion no autorizada de su contenido esta estrictamente prohibida y puede ser sancionado criminalmente. Si ha recibido este correo por error, solicitamos avisar al remitente y eliminarlo de su sistema. EMPRESAS LA POLAR S.A y sociedades relacionadas directa o indirectamente con esta, no sera responsable del uso indebido de este contenido o de los adjuntos al mismo.
Re: AMQP 0-9-1
On 11/16/2011 01:11 PM, Henry Molina wrote: How can I to setup qpidd (cpp) to speak AMQP 0-9-1 ? You can't I'm afraid. It doesn't support anything earlier than 0-10. The qpid Java broker does speak 0-9-1 (as well as 0-8 and 0-10). - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
Memory leak in QPID SWIG Python Bindings
I was running QPID 10 with the patches from QPID- (see https://issues.apache.org/jira/browse/QPID- ) and noticed there appeared to be a memory leak. import cqpid import gc inContent=[a, b] msg=cqpid.Message(inContent) outContent=msg.content id(inContent)==id(outContent) False len(gc.get_objects()) 7938 for i in xrange(1): outContent=msg.content; ... len(gc.get_objects()) 17932 Every time we point outContent to a new msg.content, the object it had been pointing at should have a reference count of zero, and be available for garbage collection, however it looks like our reference counting is off so these objects end up never getting deleted. The same is also true of messages that contain maps. I know of no issue if the message does not contain a list or a map (I also believe empty lists and maps are not affected by this). It looks like the change to qpid::messaging::Message:_get_content in 0013-Handle-amqp-list-and-amqp-map-content.patch that lets msg.content return a list or map is what is letting us see the problem, although the actual cause is a deeper issue with reference counting. Anthony (the original developer behind QPID-) put together a patch to modify the way references are incremented which I am attaching, although it is not well tested and it appears the memory increase still exists with it, so works still needs to be done. Since getting maps or lists out of messages was not particularly important, we simply circumvented this issue by editing qpid::messaging::Message:_get_content to not call decodeList or decodeMap, but the general map/list reference counting issue probably warrants some further looking into. Eric Harris Analyst Princeton Consultants, Inc. 2 Research Way Princeton, NJ 08540 609.987.8787 ext. 415 ehar...@princeton.com - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
Re: AMQP 0-9-1
Gordon, Which Java versión is ready to production? 0.10/0.12? Thanks a lot! Henry El mié, 16-11-2011 a las 13:43 +, Gordon Sim escribió: On 11/16/2011 01:11 PM, Henry Molina wrote: How can I to setup qpidd (cpp) to speak AMQP 0-9-1 ? You can't I'm afraid. It doesn't support anything earlier than 0-10. The qpid Java broker does speak 0-9-1 (as well as 0-8 and 0-10). - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org P Considere el medioambiente antes de imprimir este correo La información contenida en este mensaje y en sus documentos adjuntos, es estrictamente confidencial y privado para sus destinatarios. Cualquier uso, reproducción, divulgacion o distribucion no autorizada de su contenido esta estrictamente prohibida y puede ser sancionado criminalmente. Si ha recibido este correo por error, solicitamos avisar al remitente y eliminarlo de su sistema. EMPRESAS LA POLAR S.A y sociedades relacionadas directa o indirectamente con esta, no sera responsable del uso indebido de este contenido o de los adjuntos al mismo. P Considere el medioambiente antes de imprimir este correo La información contenida en este mensaje y en sus documentos adjuntos, es estrictamente confidencial y privado para sus destinatarios. Cualquier uso, reproducción, divulgacion o distribucion no autorizada de su contenido esta estrictamente prohibida y puede ser sancionado criminalmente. Si ha recibido este correo por error, solicitamos avisar al remitente y eliminarlo de su sistema. EMPRESAS LA POLAR S.A y sociedades relacionadas directa o indirectamente con esta, no sera responsable del uso indebido de este contenido o de los adjuntos al mismo.
Re: Broker URL - Connection Options
Hi Boris,
I don't know much about the Binding URL but I can help you with the
ConnectionURL stuff :-)
It's pretty darned hard to find a comprehensive list one needs to do a
bit of digging
There's a good list of stuff here:
http://qpid.apache.org/books/0.12/Programming-In-Apache-Qpid/html/ch03s02.html#section-jms-connection-url
but the info that you really need is here:
https://cwiki.apache.org/qpid/connection-url-format.html
Option Default Description
retries 1 The number of times to retry connection to this Broker
ssl false Use ssl on the connection
connecttimeout 3 How long in (milliseconds) to wait for the
connection to succeed
connectdelay none How long in (milliseconds) to wait before attempting
to reconnect
I've been using these in Qpid 0.10 so they are definitely still there,
I'd hope that they were still in 0.12 though haven't tried. It would be
nice if these pages got consolidated.
I just wanted to emulate the simple retry option available in the C++
qpid::messaging API so I've got code that looks like:
if (options.containsKey(reconnect))
{
String value = options.get(reconnect).toString();
if (value.equalsIgnoreCase(true))
{
retries = retries=' + Integer.MAX_VALUE + ';
connectdelay = connectdelay='5000';
}
}
Which gives (nearly!!) infinite retries with a 5 second delay between
retries.
Regards,
Frase
Ilyushonak Barys wrote:
Hi, Guru
Could you please clarify the following. It was some settings in qpid v0.7:
retries
connecttimeout
connectdelay
http://qpid.apache.org/books/0.7/Qpid-Book/html/ch11.html#BindingURLFormat
They are still in code, but there is no any info in latest docs.
Does this settings work in qpid version 0.12?
If no, what should I use to implement reconnect behavior?
Reragds,
Boris
___
The information contained in this message may be privileged and conf idential and protected from disclosure. If you are not the original intended recipient, you are hereby notified that any review, retransmission, dissemination, or other use of, or taking of any action in reliance upon, this information is prohibited. If you have received this communication in error, please notify the sender immediately by replying to this message and delete it from your computer. Thank you for your cooperation. Troika Dialog, Russia.
If you need assistance please contact our Contact Center (+7495) 258 0500 or go to www.troika.ru/eng/Contacts/system.wbp
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
Re: AMQP 0-9-1
On 11/16/2011 06:14 PM, Henry Molina wrote: Which Java versión is ready to production? 0.10/0.12? My recommendation would always be to use the latest, so 0.12. Note that there will also be a 0.14 release soon, just about to have the first RC cut with the aim of having a release at the end of November (or shortly after): https://cwiki.apache.org/confluence/display/qpid/0.14+Release - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
broker clustering with SSL?
Hi, I have a cluster of two Qpidd brokers - both C++ v0.12 (on CentOS 5.5). Both brokers have been clustering very happily so far :) Now, I've enabled both SASL and SSL on both brokers. I have several client applications I've written that can authenticate, and use SSL to talk successfully to either broker. However, I can't get the two brokers to cluster anymore (unless I disable SSL). Specifically, if I start one broker, then everything is happy (clients connect / send / receive etc). But when I try to start a second broker, the second broker begins to start up ok, but then stops after reporting error Rejected un-encrypted connection, and then shutting down the catch-up connection. Is there something I need to do to tell the brokers to use SSL for their catch-up connections? Or is require-encryption=yes incompatible with clustering? Thanks!! :) pc http://colby.id.au
