RFI: QPID-5696 - Fixes Perl handling of floats

2014-04-15 Thread Darryl L. Pierce
On Fri, Mar 21, 2014 at 11:45:34AM -0400, Justin Ross wrote: This is a single line fix to the Perl typemaps but affects any use of floats in Perl that get mapped into a Variant in the C++ code. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat

Re: How to config c++ broker persistence

2014-04-15 Thread smartdog
I am able to get persistence working. Thanks guys. -- View this message in context: http://qpid.2158936.n2.nabble.com/How-to-config-c-broker-persistence-tp7605544p7606970.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --

qpid redundantly environment and high efficiency

2014-04-15 Thread Miguel Madinaveitia
Good afternoon, everyone. I would ask for a recommendation or suggestion on how to set two (qpid) servers in a redundant environment. The scheme is as follows: We have two jboss servers and we want to write all the logs redundantly on two qpid servers with independent queues (but must contain

Re: session.sync() on AMQP 1.0 does not notify broker

2014-04-15 Thread Gordon Sim
On 04/15/2014 01:53 PM, Rob Godfrey wrote: From an AMQP 1.0 perspective, the broker really shouldn't need telling. The question is really how to determine if/when the broker should flush any writes to disk. Durable messages will only be considered settled when the broker can be sure the enqu

Re: session.sync() on AMQP 1.0 does not notify broker

2014-04-15 Thread Rob Godfrey
>From an AMQP 1.0 perspective, the broker really shouldn't need telling. The intention was that a container may decide to batch information it has on hand, but it should always be "prompt" in informing its peers of disposition changes. So its valid to wait until you've finished process a batch of

session.sync() on AMQP 1.0 does not notify broker

2014-04-15 Thread Pavel Moravec
Hello, I have spotted a performance-impacting lack in AMQP 1.0 implementation of session.sync() in C++ client. On AMQP 0-10, the method sends execution.sync frame to the broker, asking for prompt delivery status to be sent. But 1.0 client does not invoke any such command. For performance impact,