qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gordon Sim <g...@redhat.com>
Subject Re: Error creating connection: The following SASL mechanisms [PLAIN] specified by the client are not supported by the broker
Date Wed, 15 Dec 2010 10:36:20 GMT
On 12/15/2010 10:03 AM, junkmailxx@centrum.cz wrote:
> I am trying to reach a qpidd broker started with the --auth no option from a Java client
(both version 0.8) and am receiving the following exception:
>
> javax.jms.JMSException: Error creating connection: The following SASL mechanisms [PLAIN]
specified by the client are not supported by the broker
> at org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:286)
> ....
>
> My JNDI/JMS configuration is:
>
> java.naming.factory.initial = org.apache.qpid.jndi.PropertiesFileInitialContextFactory
> connectionfactory.qpidConnectionfactory = amqp://guest:guest@clientid/abcd?brokerlist='tcp://localhost:5672'
> destination.mainSend = direct://amq.direct//step.01
>
> It worked just fine in 0.6 but no success now in 0.8.
>
> What am I doing wrong? Any clues?

Try turn ing on tracing on the broker side (--log-enable info+ 
--log-enable trace+:amqp_0_10 is how I do that). You should see 
something like the following:

> 2010-12-15 10:31:50 trace SENT 127.0.0.1:45652 INIT(0-10)
> 2010-12-15 10:31:50 trace SENT [127.0.0.1:45652]: Frame[BEbe; channel=0; {ConnectionStartBody:
server-properties={qpid.federation_tag:V2:36:str16(06f558c7-37a1-4d15-a0fb-4586355a6598)};
mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)}; locales=str16{V2:5:str16(en_US)};
}]
> 2010-12-15 10:31:50 trace RECV [127.0.0.1:45652]: Frame[BEbe; channel=0; {ConnectionStartOkBody:
client-properties={qpid.client_pid:F4:int32(6173),qpid.client_process:V2:16:str16(Qpid Java
Client),qpid.session_flow:F4:int32(1)}; mechanism=PLAIN; response=xxxxxx; }]
> 2010-12-15 10:31:50 trace SENT [127.0.0.1:45652]: Frame[BEbe; channel=0; {ConnectionTuneBody:
channel-max=32767; max-frame-size=65535; heartbeat-min=0; heartbeat-max=120; }]

With --auth no specified, qpidd should always offer ANONYMOUS and PLAIN 
(though it doesn't actually attempt to verify users in the PLAIN case in 
anyway) as seen here in the ConnectionStart. The client should then be 
able to choose PLAIN without issue (as seen in the following 
ConnectionStartOk).

What is the interaction you are seeing here? What platform are you 
running the broker on?

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


Mime
View raw message