thanks a lot. I tried both PRE_ACQUIRED NOT_ACQUIRED. Is there any
performance overhead involved in any of these 2 options?
Also i wanted to know whether ACCEPT_MODE_EXPLICIT/ACCEPT_MODE_NONE has any
performance overhead?
Is there any document available that gives performance overheads of
Olivier Utkala wrote:
All files seems to be in right place, the user exists in
/opt/qpid/var/lib/qpidd/qpidd.sasldb
I am sure that user and pwd are correct in client.
File /opt/qpid/etc/sasl2/qpidd.conf contains:
This is probably not being picked up by the cyrus-sasl libraries. I
think it has
ft420 wrote:
thanks a lot. I tried both PRE_ACQUIRED NOT_ACQUIRED. Is there any
performance overhead involved in any of these 2 options?
I doubt either option is as fast as the common path (which is where most
optimisation has focused so far). I'd suggest trying it out to see if it
meets
do you mean without persistence plugin creating durable queue is not
possible? what to do with the files at the link you have mentioned in your
earlier post?
i did save all the files in store folder following the same directory
structure as at the link..
One more problem:
I modified the
On Mon, Mar 23, 2009 at 12:09 PM, Gordon Sim g...@redhat.com wrote:
ft420 wrote:
do you mean without persistence plugin creating durable queue is not
possible?
No, unfortunately not. We do want a plugin that can be part of Qpid but it
would have to rely only on ASF compatible libraries and
Aidan Skinner wrote:
On Mon, Mar 23, 2009 at 12:09 PM, Gordon Sim g...@redhat.com wrote:
ft420 wrote:
do you mean without persistence plugin creating durable queue is not
possible?
No, unfortunately not. We do want a plugin that can be part of Qpid but it
would have to rely
I did try following steps:
br./bootstrap then
br./configure which gives following error::
br./configure: line 19936: syntax error near unexpected token `'
br./configure: line 19936: ` nbsp;test $fail = 1 amp;amp;'
