Re: Operation not permitted (qpid/sys/epoll/EpollPoller.cpp:254)

2010-01-27 Thread Jason Schlauch
On Wed, Jan 27, 2010 at 12:37 PM, Steve Huston wrote: > > Right - this seems to be the main problem to solve here. Could you > please open a jira for it? I worked around it by scaling back my daemon's file descriptor closing to just stdin, stdout, and stderr. I did, however, open a JIRA for it:

Re: all subscribers not equal?

2010-01-27 Thread Robert Godfrey
Hi Mark, I can give an outline of how the Java Broker distributes messages between subscriptions... I'm not familiar with anything the Python client may do... In general, when there is no backlog in the queue, the Java Broker will round-robin between subscriptions which have available credit. If

all subscribers not equal?

2010-01-27 Thread mARK bLOORE
I am using the java broker 0.5 and the python client. I have a queue with one publisher and (usually) three subscribers. The publisher sends messages at a fairly constant rate. The subscribers take messages in a single thread at an unlimited rate, put them in a buffer, and ack the messages immedia

RE: Operation not permitted (qpid/sys/epoll/EpollPoller.cpp:254)

2010-01-27 Thread Steve Huston
Hi Jason, > On Mon, Jan 25, 2010 at 6:54 PM, Steve Huston > wrote: > > alwaysReadableFd is for a pipe - is there a chance you've closed it? > > I think there is. It looks like the static scope of > alwaysReadable and alwaysReadableFd cause them to get > initialized before main(). When my dae

Re: Debian packages

2010-01-27 Thread Gordon Sim
On 01/27/2010 02:13 PM, Cajus Pollmeier wrote: Debian releases and/or qpid releases? I can provide packages for the current stable debian release and the current stable qpid release. So - if 0.6 is released, I can make 0.6 packages which will replace version 0.5 in the repository. Theoreticall

Re: Debian packages

2010-01-27 Thread Cajus Pollmeier
Debian releases and/or qpid releases? I can provide packages for the current stable debian release and the current stable qpid release. So - if 0.6 is released, I can make 0.6 packages which will replace version 0.5 in the repository. Theoretically I can upload them to the debian repository if

Re: Debian packages

2010-01-27 Thread Carl Trieloff
On 01/27/2010 03:32 AM, Cajus Pollmeier wrote: Hi - here's a re-post from dev, I was looking for some ready to use debian packages of qpid and didn't find anything. While playing with the build process I managed to do packages (version 0.5 in the moment) for qpid-cpp and qpid-python as some ki

Notification on message expiry

2010-01-27 Thread Ramez Mani
Hi, Is it possible to get notified if a message(with TTL set) expires? Basically I want to store transaction context in queue(with ttl) and send a request. So on response will retrieve the context from queue. If no response(event/context not dequeued) within ttl, should get a notifi

Re: timeouts

2010-01-27 Thread Martin Ritchie
2010/1/6 Jen Andre : > > > I can't use the JMS API because of this bug: > http://old.nabble.com/-jira--Created:-(QPID-1875)-Can't-create-durable-queues-that-use-amq.topic-due-to-error-in-BindingURLParser.-td23726482.html. > I need to create a durable queue bound to a topic. If there some > workar

Re: Persistence / Durability problems with 0.5 python client and C++ broker.

2010-01-27 Thread Gordon Sim
On 01/26/2010 07:18 PM, Inoshiro Linden wrote: Hello, I have not discovered how to send persistent messages on a durable queue using the python client and the c++ broker. There are three issues: documentation, the python code/exception, and the chat channel: The documentation: The documentat

Debian packages

2010-01-27 Thread Cajus Pollmeier
Hi - here's a re-post from dev, I was looking for some ready to use debian packages of qpid and didn't find anything. While playing with the build process I managed to do packages (version 0.5 in the moment) for qpid-cpp and qpid-python as some kind of fall-out. They may not be 100% perfect bec

Re: Maximum message/header length

2010-01-27 Thread Gordon Sim
On 01/26/2010 10:49 PM, Rafael Schloming wrote: I believe the JMS client will send multiple header frames if the headers are large. I would guess from this that the broker isn't defragmenting multiple header frames properly. Correct, the c++ framing does not handle multi-frame header or command