Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    This exception could rise due to a connection timeout.

Solutions on the web

via oodt-user by Chris Mattmann, 7 months ago
expected:<[test-queue-1, quick]> but was:<[quick, test-queue-1]>
via oodt-user by kelly@apache.org, 1 year ago
expected:<[test-queue-1, quick]> but was:<[quick, test-queue-1]>
via oodt-user by kelly@apache.org, 1 year ago
expected:<[test-queue-1, quick]> but was:<[quick, test-queue-1]>
via oodt-user by Chris Mattmann, 1 year ago
expected:<[test-queue-1, quick]> but was:<[quick, test-queue-1]>
via oodt-user by Tom Barber, 1 year ago
expected:<[test-queue-1, quick]> but was:<[quick, test-queue-1]>
via oodt-user by Tom Barber, 1 year ago
expected:<[test-queue-1, quick]> but was:<[quick, test-queue-1]>
junit.framework.AssertionFailedError: expected:<[test-queue-1, quick]> but was:<[quick, test-queue-1]>	at junit.framework.Assert.fail(Assert.java:47)	at junit.framework.Assert.failNotEquals(Assert.java:280)	at junit.framework.Assert.assertEquals(Assert.java:64)	at junit.framework.Assert.assertEquals(Assert.java:71)	at org.apache.oodt.cas.resource.queuerepo.TestXmlQueueRepository.testMapping(TestXmlQueueRepository.java:64)