Hi Robbie, We found the problem. The C++ broker was allowing anonymous connections and we were sending the wrong password. So we thought our code was correct since it worked against the C++ broker (--auth no).
Normally I would consider taking a bone headed mistake like this to my grave :), but there was an oddity with the windows C++ broker that threw us off the trail: The C++ broker from RiverAce only seem so use windows accounts to authenticate. Can anyone explain why this is the case? So, the java broker is doing what it should be doing. Sorry! thanks, Adam On Mon, Jan 31, 2011 at 6:20 PM, Robbie Gemmell <[email protected]>wrote: > Hi Adam, > > Can you post a sample of the consumer/producer code you are using, along > with your connection URLs, what JVM version you are on etc. > > Robbie > > > -----Original Message----- > > From: Adam Crain [mailto:[email protected]] > > Sent: 31 January 2011 17:10 > > To: [email protected] > > Subject: Re: java broker authentication > > > > We've further narrowed this down. It seems to be a problem with the > > java > > client talking to the java broker. The python client seems to work just > > fine > > with the account guest:guest. > > > > -Adam > > > > On Sun, Jan 30, 2011 at 12:55 AM, Adam Crain > > <[email protected]>wrote: > > > > > Hi, > > > > > > I'm trying to run against the java broker. Running my unit tests > > which > > > succeed against the C++ broker, the log tells me the broker rejects > > my > > > user/password of guest:guest > > > > > > QpidBrokerConnection - Connecting to > > qpid:/[email protected]:5672/localhost > > > ConnectionException: Error processing data: > > > javax.security.sasl.SaslException: Authentication failed > > > > > > How to debug authentication failures? > > > > > > thanks, > > > Adam > > > > > > > > > > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > >
