I believe this is an issue with the Windows' C++ broker code that was
resolved recently by Gordon Sim. If you are up for checking the current
source code out from subversion, that should do it. Else I believe this will
be fixed in the 0.12 release coming up within a few weeks or so.

-Steve

-----Original Message-----
From: tnowicki [mailto:nowic...@setcorp.com] 
Sent: Thursday, July 14, 2011 1:36 PM
To: users@qpid.apache.org
Subject: java client, c++ broker, no authentication

I saw some traffic on the subject back in 2009 but could not gleen an
answer.
I am running 0.10 c++ broker with --auth no, using the java build for 0.10.
The first problem that I have is that the URL is not accepted without a
username and password. I added guest:guest assuming that it won't care on
the broker side if running no authentication but got the following exception
from the client when attempting a connection:

org.apache.qpid.AMQConnectionFailureException: The following SASL mechanisms
[PLAIN] specified by the client are not supported by the broker [error code
200: reply success]

using URL:
amqp://guest:guest@clientid/test?brokerlist='tcp://127.0.0.1:5672'

I saw some discussion on this before but did not see a solution. Are there
any suggestions on how to connect successfully java client to c++ broker?
For various reasons, I need to run the broker with no authentication.

BTW, this is on WindowsXP.

Thanks,
-Tony



--
View this message in context:
http://apache-qpid-users.2158936.n2.nabble.com/java-client-c-broker-no-authe
ntication-tp6584247p6584247.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org




---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org

Reply via email to