[Java Broker] SimlpeACLTest intermittent failures
-------------------------------------------------
Key: QPID-873
URL: https://issues.apache.org/jira/browse/QPID-873
Project: Qpid
Issue Type: Bug
Components: Java Broker, Java Tests
Reporter: Rob Godfrey
Occaisionally seeing erors running SimpleACLTest on Quad core machine, e.g.
-------------------------------------------------------------------------------
Test set: org.apache.qpid.server.security.acl.SimpleACLTest
-------------------------------------------------------------------------------
Tests run: 17, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.172 sec <<<
FAILURE!
testServerCreateTemporyQueueInvalid(org.apache.qpid.server.security.acl.SimpleACLTest)
Time elapsed: 60.365 sec <<< ERROR!
org.apache.qpid.AMQConnectionFailureException: -1 [error code -1: unknown code]
at org.apache.qpid.client.AMQConnection.<init>(AMQConnection.java:459)
at org.apache.qpid.client.AMQConnection.<init>(AMQConnection.java:326)
at
org.apache.qpid.server.security.acl.SimpleACLTest.testServerCreateTemporyQueueInvalid(SimpleACLTest.java:439)
Tracing the underlying cause you get:
java.lang.NullPointerException
at
org.apache.qpid.server.security.auth.database.PropertiesPrincipalDatabase.setPassword(PropertiesPrincipalDatabase.java:72)
at
org.apache.qpid.server.security.auth.sasl.UsernamePasswordInitialiser$ServerCallbackHandler.handle(UsernamePasswordInitialiser.java:71)
at
com.sun.security.sasl.CramMD5Server.evaluateResponse(CramMD5Server.java:152)
at
org.apache.qpid.server.security.auth.manager.PrincipalDatabaseAuthenticationManager.authenticate(PrincipalDatabaseAuthenticationManager.java:220)
at
org.apache.qpid.server.handler.ConnectionSecureOkMethodHandler.methodReceived(ConnectionSecureOkMethodHandler.java:71)
at
org.apache.qpid.server.handler.ServerMethodDispatcherImpl.dispatchConnectionSecureOk(ServerMethodDispatcherImpl.java:422)
at
org.apache.qpid.framing.amqp_0_9.ConnectionSecureOkBodyImpl.execute(ConnectionSecureOkBodyImpl.java:113)
at
org.apache.qpid.server.state.AMQStateManager.methodReceived(AMQStateManager.java:204)
at
org.apache.qpid.server.protocol.AMQMinaProtocolSession.methodFrameReceived(AMQMinaProtocolSession.java:295)
at
org.apache.qpid.framing.AMQMethodBodyImpl.handle(AMQMethodBodyImpl.java:93)
at
org.apache.qpid.server.protocol.AMQMinaProtocolSession.frameReceived(AMQMinaProtocolSession.java:235)
Which is due to a bug in the PropertiesPrincipalDatabase; however we should
never get to this point of the code in this test (we should be using a plain
password file database).
Looking further the reason is that failover is occuring at the same time that
the InVM broker is being killed. Failover shouldn't occur for Authentication
exceptions; instead AuthenticationExceptions should be hard errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
