Keith Wall created QPID-4090:
--------------------------------

             Summary: Can't connect from Java Client to Java Broker when Broker 
uses Base64MD5PasswordFilePrincipalDatabase principal database (0-10 protocol 
only)
                 Key: QPID-4090
                 URL: https://issues.apache.org/jira/browse/QPID-4090
             Project: Qpid
          Issue Type: Bug
          Components: Java Broker, Java Client
    Affects Versions: 0.17
            Reporter: Keith Wall


If I config the Java Broker to use Base64MD5PasswordFilePrincipalDatabase 
principal database, I am unable to connect from the Java client if I am using 
the 0-10 protocol.  

The exception seen client side is as follows:

{code}
org.apache.qpid.AMQException: Cannot connect to broker: Callback handler with 
support for AuthorizeCallback required [error code 320: connection forced]
        at 
org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:239)
        at 
org.apache.qpid.client.AMQConnection.makeBrokerConnection(AMQConnection.java:588)
        at org.apache.qpid.client.AMQConnection.<init>(AMQConnection.java:367)
        at 
org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:121)
        at org.apache.qpid.example.Hello.runTest(Hello.java:51)
        at org.apache.qpid.example.Hello.main(Hello.java:40)
Caused by: org.apache.qpid.transport.ConnectionException: Callback handler with 
support for AuthorizeCallback required
        at 
org.apache.qpid.transport.ConnectionException.rethrow(ConnectionException.java:67)
        at org.apache.qpid.transport.Connection.connect(Connection.java:269)
        at 
org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:219)
        ... 5 more
Caused by: org.apache.qpid.transport.ConnectionException: Callback handler with 
support for AuthorizeCallback required
        at org.apache.qpid.transport.Connection.closeCode(Connection.java:531)
        at 
org.apache.qpid.transport.ConnectionDelegate.connectionClose(ConnectionDelegate.java:75)
        at 
org.apache.qpid.transport.ConnectionDelegate.connectionClose(ConnectionDelegate.java:1)
        at 
org.apache.qpid.transport.ConnectionClose.dispatch(ConnectionClose.java:91)
        at 
org.apache.qpid.transport.ConnectionDelegate.control(ConnectionDelegate.java:49)
        at 
org.apache.qpid.transport.ConnectionDelegate.control(ConnectionDelegate.java:1)
        at org.apache.qpid.transport.Method.delegate(Method.java:163)
        at org.apache.qpid.transport.Connection.received(Connection.java:376)
        at org.apache.qpid.transport.Connection.received(Connection.java:1)
        at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:97)
        at 
org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:183)
        at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:131)
        at org.apache.qpid.transport.network.Frame.delegate(Frame.java:128)
        at 
org.apache.qpid.transport.network.Assembler.received(Assembler.java:102)
        at 
org.apache.qpid.transport.network.Assembler.received(Assembler.java:1)
        at 
org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:189)
        at 
org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:105)
        at 
org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:1)
        at 
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:152)
        at java.lang.Thread.run(Thread.java:662)
{code}

If I use protocols 0-8...0-9-1, all works well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to