Thanks Gordon. Just to clarify default behaviour - for Java clients the default
is 120s but for C++/Python clients the heartbeating is off and must be
explicitly set? In other words, C++/Python clients that are dead (OS crash,
network problems, client is hung) will be never removed from broker
In my qmf.console based app, I was trying to figure out how to piggy-back
my browsing of a queue
on the existing broker's connection, using
broker.conn.session('somename'), and while pdb was trying to print a stack
trace, the __str__ method of the qpid.connection.Connection instance got
called. T
I have been trying to do this for a few days. My python is not very strong.
I have been trying combinations and permutions of:
qpid-config -b amqps://localhost , ssl_certfile="/path/to/certfile",
ssl_keyfile="/path/to/keyfile" --sasl-mechanism='EXTERNAL'
I am currently using qpid 0.18.
An exampl
Hi Jason,
thanks - I'll look into this. The changes to the broker to fix the
deadlock would have introduced more synchronization, but I wouldn't have
expected it to make a significant difference to performance. I've been a
bit snowed under with other stuff for the last few days - but I'll try to
On 6 April 2013 10:40, Fraser Adams wrote:
> I'm afraid that I've not had time yet to begin my journey down the AMQP
> 1.0 path. I don't suppose that you can point me to a quick reference that
> points to the key differences? I'll take a look at the spec when I get a
> bit of time, but I'd quite
On 9 April 2013 15:28, Jan Bares wrote:
> I cannot find any documentation about how C++ broker detects dead clients.
> In client I can set heartbeat/idle_timeout - this will allow client to
> detect dead broker but I have not found any documentation how broker can
> detect dead clients. It even s
Hi Michal,
There is no explicit flow-to-disk, but rather an implicit effect from the
way the messages are referenced. What the broker does is store persistent
messages on disk and reference them with soft references, such that if the
JVM needs to garbage collect them to make room for additional me
Hi,
I cannot find any documentation about how C++ broker detects dead clients. In
client I can set heartbeat/idle_timeout - this will allow client to detect dead
broker but I have not found any documentation how broker can detect dead
clients. It even seems like broker doesn't use TCP_KEEPALIVE
