Wiki cleanup

2013-07-15 Thread Justin Ross
Hi, everyone. I've done a first pass at cleaning up our wiki. https://cwiki.apache.org/confluence/display/qpid/Index I tried to capitalize on the structure that already developed there organically. As I ran through the pages, they fell into three categories: 1. Obviously useless stuff (emp

Re: tcp-nodelay on broker

2013-07-15 Thread Andrew Stitcher
On Sat, 2013-07-13 at 02:47 -0600, Rajesh Khan wrote: > The manual states > > "For latency sensitive applications, setting tcp-nodelay on qpidd and on > client connections can help reduce the latency" > > I know how to set this option for clients(Receiver). How do we set it up > for qpidd(broker)

Re: Handling queue overflows

2013-07-15 Thread Jimmy Jones
Hi Gordon, Thanks for your swift and helpful reply! I had wrongly assumed that the pagesize was fixed at the platform page size. I think paging should suit my needs, I'll give it a go once 0.24 is released. I don't think i'll now need it, but is there interest in a limit policy of sending to a

Re: Handling queue overflows

2013-07-15 Thread Fraser Adams
This thread interests me somewhat, in particular with respect to the new paging mechanism and also the backup engine in 0.24 (and I guess trunk). Is there any info/examples on how to set these up and have a play? Are they AMQP 0.10/1.0 neutral or do they have dependencies on 1.0? What I'd qu

JMS API incomplete ?

2013-07-15 Thread Axel Podehl
Hi all, as I understand from a previous post and from my testing, there is no way to retrieve all AMQP header properties (e.g. contentType) just using the JMS API. In my case, I have a generic JMS record&replay program and would want to use it to record an AMQP message and replay it, simply using

Re: Please read: Change to C++ broker default behavior wrt QMF

2013-07-15 Thread Bill Freeman
Since I did make my tool work with v2, and I am currently discarding v1 messages (*), I think that this won't impact me. (* I have to discard the v1 messages, since we are not, as previously proposed, delivering the v2 messages to a separate Console (callback) method. So I'm slightly less certain

Re: Handling queue overflows

2013-07-15 Thread Gordon Sim
On 07/15/2013 02:01 PM, Jimmy Jones wrote: Hi, I've got a system which can sometimes be a bit bursty, which would exhaust system memory if the queues were left unchecked. Therefore I've been using ring queues, which solve the problem quite nicely, apart from what happens to the "excess" messag

Re: Swigged Python bindings...

2013-07-15 Thread Darryl L. Pierce
On Fri, Jul 12, 2013 at 09:58:19AM -0400, Alan Conway wrote: > So is it the case that we have 2 versions of the Qpid messaging > interface: one in python and one swigged? > > In that case how about qpid.messaging and qpid.messagingc? Its the > package that's different, not the containing project.

Handling queue overflows

2013-07-15 Thread Jimmy Jones
Hi, I've got a system which can sometimes be a bit bursty, which would exhaust system memory if the queues were left unchecked. Therefore I've been using ring queues, which solve the problem quite nicely, apart from what happens to the "excess" messages. Ideally I'd like to buffer them to disk

Re: tcp-nodelay on broker

2013-07-15 Thread Rajesh Khan
Here is what I did D:\qpid-0.18\qpid-0.18\cpp\src\Debug>qpidd --tcp-nodelay --auth=no 2013-07-15 02:37:15 [Broker] notice SASL disabled: No Authentication Performed 2013-07-15 02:37:15 [Security] error Failed to initialise SSL listener: Locating certificate Rajesh-PC in store My Cannot find object

Re: Qpid broker in OSGI container

2013-07-15 Thread Xavier Millieret
ok, thanks 2013/7/12 Robbie Gemmell > I'm not aware of anyone planning work in this area, no. Patches welcome :) > > Robbie > > On 12 July 2013 08:37, Xavier Millieret >wrote: > > > Hi Robbie, > > > > Thank you Robbie, do you have an idea, if it's planed ? > > > > > > 2013/7/11 Robbie Gemmell