+1 for (a)
- Original Message -
> From: "Gordon Sim"
> To: users@qpid.apache.org
> Sent: Tuesday, August 7, 2012 2:11:52 PM
> Subject: Straw Poll: proposal to remove certain features from qpidd
>
> So, to follow up and summarise this thread so far, the only
> contentious
> point has been
I really like the refactor, and would rather see it sooner than later, so I'm
good with (a)!
-K
- Original Message -
> So, to follow up and summarise this thread so far, the only
> contentious
> point has been the loss of the 'flow to disk' functionality.
>
> Though the current solution
Thanks to everyone who has voiced an opinion so far. My plan is to start
getting the patch on to trunk tomorrow. If anyone is not happy with
option (a), has other concerns or simply needs more time, make yourself
heard!
-
To u
Hi,
I'm using the C++ messaging API to connect to the broker. cyrus-sasl is
available.
After changing /etc/sasl2/qpidd.conf, I receive this error:
2012-08-09 17:55:20 warning Closing connection due to internal-error:
Sasl error: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS
failure. Mi
On 08/09/2012 02:52 PM, Davide Anastasia wrote:
Hi Gordon,
I'm using the C++ broker, v. 0.14, the one shipped with RHEL6.
I have used the guide in your page to set up the Kerberos server,
without success.
Ok, and what client(s) are you using to connect?
How can I explicitly require GSSAPI as
Hi Davide,
add to /etc/sasl2/qpidd.conf:
mech_list: GSSAPI
to stick qpid broker in enforcing just that type of SASL mechanism.
If you require to set it in the client, then it depends on what client/tool do
you use. I.e.
qpid-config --sasl-mechanism=GSSAPI ..
C++ spout/drain: ./drain --connecti
Hi Gordon,
I'm using the C++ broker, v. 0.14, the one shipped with RHEL6.
I have used the guide in your page to set up the Kerberos server,
without success.
How can I explicitly require GSSAPI as the mechanism? How can I change
it in the /etc/sasl2/qpidd.conf file? I'm just checking whether the
cy
Hi Alan,
Thanks for getting back to me.
Some of limitations would make this a no go for me at the moment.
I'm guessing the "older cluster" module will be phased out gradually?
Obviously the burden of maintaining both strategies long term will be
a pain...
By "bind address" - I mean, when qpidd st
On 08/08/2012 05:00 PM, Davide Anastasia wrote:
Hi All,
Can anybody point me to a guide that could help me to setup Kerberos to
work with Qpid?
Which broker are you using? qpidd (i.e. c++) or qpid-server (Java).
If the former, is
http://qpid.apache.org/books/0.16/AMQP-Messaging-Broker-CPP-Bo
