I would like to request merging the fix for QPID-3582: Client reporting "Unable to load custom SASL providers" during connection.
The client logs out an error level message on each initial use because it does something twice that it should only do once. This is a regression from previous releases and although it doesnt actually represent anything happening that will cause users a problem, it will at least make them think something to be concerned about has happened. Robbie On 30 November 2011 19:55, Andrew Stitcher <[email protected]> wrote: > On Wed, 2011-11-30 at 13:24 -0500, [email protected] wrote: >> Hi, everyone. There were no further changes against RC1 last week. This >> week we have just one: >> >> r1207741 | grkvlt | 2011-11-28 22:13:55 -0500 (Mon, 28 Nov 2011) | 1 >> line >> QPID-3489: Added org.apache.qpid.server.message to exported packages >> for broker >> >> I will produce the second release candidate tomorrow, and I will propose >> it for release. To my impression, the rate of change, and requests for >> changes, have diminished, and testing reports have been positive. If you >> disagree, I'm eager to talk about it. > > I have a request for a bug fix: > > QPID-3654: ANONYMOUS SASL mechanism does not work on Java client > > https://issues.apache.org/jira/browse/QPID-3654 > > It's an almost trivial one line fix, seems very safe (to me at least) > and it enables a very convenient (if not truly necessary) feature for > the Java client. > > Any volunteers for a quick review? > > Andrew > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
