Hello, 

I'm attempting to connect to MQLight with the Qpid JMS API for AMQP 1.0.

The code (in *Scala*): 
    /val host = "localhost"
    val port = 5672
    val user = "guest"
    val pass = "guest"
    val isSSL = false
    val clientId = "test-client"

    val connectionFactory = new ConnectionFactoryImpl(host, port, user,
pass, clientId, isSSL)
    val connection = connectionFactory.createConnection()

    val session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE )
/

The exception I'm getting: 
/Exception in thread "main" javax.jms.JMSException: AMQXR0029E: sasl
mechanisms of client and server must match.
        at
org.apache.qpid.amqp_1_0.jms.impl.SessionImpl.<init>(SessionImpl.java:97)
        at
org.apache.qpid.amqp_1_0.jms.impl.ConnectionImpl.createSession(ConnectionImpl.java:231)
        at
org.apache.qpid.amqp_1_0.jms.impl.ConnectionImpl.createSession(ConnectionImpl.java:210)
        at com.monitise.s2s.Main$.main(MyRouteMain.scala:26)
        at com.monitise.s2s.Main.main(MyRouteMain.scala)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)/

I'm pretty sure both the client and the server use "PLAIN" sasl mechanism.
This snippet work fine with ActiveMQ, so I'm guessing there must be a
problem with how MQ Light responds. 

BTW, this type of question was already asked on the IBM forums, and they
pointed to the Qpid community for help :)

Thanks for any suggestions!





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/MQLight-with-Apache-Qpid-JMS-AMQP-1-0-tp7615707.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to