Re: Any one have compiled qpid on Pidora?

sundawei Wrote :--- > It take so long > to compile from the source and at last ended with error. What is that error you got while compiling ? -- View this message in context: http://qpid.2158936.n2.nabble.com/Any-one-have-compiled-qpid-on-Pidora-tp7594460p7597238.html Sent from t

Re: tcp-nodelay on broker

-Andrew that's good catch. Thank you -- View this message in context: http://qpid.2158936.n2.nabble.com/tcp-nodelay-on-broker-tp7595208p7597237.html Sent from the Apache Qpid users mailing list archive at Nabble.com. - To uns

Re: JMS client reconnect to qpidc

On 08/20/2013 05:58 PM, Aleš Trček wrote: Hi all, I tested a situation where I have JMS consumers (and producers for that matter) attached to some queues on qpidc-0.22 broker and then I stop the broker and start it again (with persistence module). The connection is not reestablished, and subs

JMS client reconnect to qpidc

Hi all, I tested a situation where I have JMS consumers (and producers for that matter) attached to some queues on qpidc-0.22 broker and then I stop the broker and start it again (with persistence module). The connection is not reestablished, and subsequent calls to MessageConsumer.receive() al

Re: C++ qpid::messaging::MessagingException::detail

On 08/20/2013 02:27 PM, Andrew Stitcher wrote: Gordon The (public) detail member of qpid::messaging::MessagingException struct doesn't seem to be used anywhere. * Is it in fact used somewhere I didn't notice? * I'm minded to remove it going forward, even though this would technically be an ABI

RE: Qpid C++ broker & JMS rollback not working properly

You're too fast for me :) (have seen your mail, but had meetings & stuff). Anyway, this was obviously the problem, since sure enough, with non-priority queues it worked, I just didn't try it before... So, I applied the patch, rebuilt the broker and now it works again. Thank you very much for the

Re: tcp-nodelay on broker

On Tue, 2013-08-20 at 01:37 -0700, NimbusParc wrote: >yes, --tcp-nodelay became default in qpidc-0.24.But, still it is > showing as an optional one in *qpidd -h * menu. Need to edit that one. Well, you can still turn it off if you really want to with "--tcp-nodelay no" (assuming your ve

C++ qpid::messaging::MessagingException::detail

Gordon The (public) detail member of qpid::messaging::MessagingException struct doesn't seem to be used anywhere. * Is it in fact used somewhere I didn't notice? * I'm minded to remove it going forward, even though this would technically be an ABI breakage - if it is never set no one can actually

Re: Qpid C++ broker & JMS rollback not working properly

On 08/20/2013 11:57 AM, Gordon Sim wrote: On 08/19/2013 11:28 PM, Aleš Trček wrote: Is there something broken/changed in qpidc 0.22 or am I missing something? There were some major changes to qpidd between 0.18 and 0.22 and I can see a bug that I think might be at the root of this. Can you sen

Re: Qpid C++ broker & JMS rollback not working properly

On 08/19/2013 11:28 PM, Aleš Trček wrote: Hi all, I have a rather nasty problem I can't seem to be able to solve, using the following setup: -qpidc-0.22 broker -qpid JMS client (different versions tried) I create a transacted session and consume messages from the queue. When I call commit(),

Re: tcp-nodelay on broker

yes, --tcp-nodelay became default in qpidc-0.24.But, still it is showing as an optional one in *qpidd -h * menu. Need to edit that one. -- View this message in context: http://qpid.2158936.n2.nabble.com/tcp-nodelay-on-broker-tp7595208p7597117.html Sent from the Apache Qpid users mail

Re: Help:qpid-python client doesn't work for qpid-0.22

These Exceptions tells the Installation was not successful. To install properly .. 1. first download from official website http://qpid.apache.org/download.html .2. Untar it and enter into qpid-tools directory.3. Run * ./setup.py build * and