Quoting Carl Trieloff cctriel...@redhat.com:
yes, place the new file and then there is a QMF method that can be
called to relaod
the ACL. If the new ACL file has errors, the old files runs will
stay in place.
Hi,
I tried to use the library org.apache.qpid.console to access the class
On 02/28/2010 10:15 PM, Michael Jeung wrote:
Hi guys,
I notice that a couple other vendors have adopted the 0-91 amqp
specification. (In particular, OpenAMQ supports 0-91 and RabbitMQ has
plans to support 0-91 according to its website.)
I wanted to ask - does Qpid also have plans to support
On 03/01/2010 07:19 AM, Joan Bellver Faus wrote:
Quoting Carl Trieloff cctriel...@redhat.com:
yes, place the new file and then there is a QMF method that can be
called to relaod
the ACL. If the new ACL file has errors, the old files runs will
stay in place.
Hi,
I tried to use the
Quoting Carl Trieloff cctriel...@redhat.com:
On 03/01/2010 07:19 AM, Joan Bellver Faus wrote:
Quoting Carl Trieloff cctriel...@redhat.com:
yes, place the new file and then there is a QMF method that can be
called to relaod
the ACL. If the new ACL file has errors, the old files runs will
On 03/01/2010 09:10 AM, Joan Bellver Faus wrote:
Quoting Carl Trieloff cctriel...@redhat.com:
On 03/01/2010 07:19 AM, Joan Bellver Faus wrote:
Quoting Carl Trieloff cctriel...@redhat.com:
yes, place the new file and then there is a QMF method that can be
called to relaod
the ACL. If the
OK, so seems like there's at least a partial resolution to this, which is to
use the latest trunk build, due to the bug QPID-1893. This bug relates to the
java client not generating heartbeats, fixed 12-Jan-2010.
I'm not entirely sure how not properly responding to heartbeats causes the
resend
