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 MuleSoft JIRA by Daniel Zapata, 1 year ago
via MuleSoft JIRA by Daniel Zapata, 1 year ago
via incubator-kafka-users by Neha Narkhede, 2 years ago
expected:<5> but was:<2>
via continuum-dev by Roald Bankras, 9 months ago
expected:<0> but was:<1>
via sourceforge.net by Unknown author, 2 years ago
expected:<2> but was:<0>
via apache.org by Unknown author, 1 year ago
expected:<10> but was:<0>
junit.framework.AssertionFailedError: expected:<5> but was:<0>	at junit.framework.Assert.fail(Assert.java:47)	at junit.framework.Assert.failNotEquals(Assert.java:277)	at junit.framework.Assert.assertEquals(Assert.java:64)	at junit.framework.Assert.assertEquals(Assert.java:195)	at junit.framework.Assert.assertEquals(Assert.java:201)	at com.mulesource.qatests.retry.jms.JmsRetrySanityAsynchronousTestCase.testNormalOperation(JmsRetrySanityAsynchronousTestCase.java:32)