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

    Check your pattern declaration or check your assert declaration.

Solutions on the web

via Kuali JIRA by Mike Riley, 1 year ago
expected:<LOCK_FAILURE> but was:<FOUND>
via Kuali JIRA by Mike Riley, 2 years ago
expected:<LOCK_FAILURE> but was:<FOUND>
via GitHub by keith-turner
, 1 year ago
expected:<39> but was:<15>
via GitHub by anuraaga
, 1 year ago
expected:<3> but was:<2>
via GitHub by phax
, 2 years ago
expected:<sha512> but was:<null>
via Google Groups by Peter Firmstone, 9 months ago
expected:<0> but was:<3>
java.lang.AssertionError: expected:<LOCK_FAILURE> but was:<FOUND>	at org.junit.Assert.fail(Assert.java:91)	at org.junit.Assert.failNotEquals(Assert.java:645)	at org.junit.Assert.assertEquals(Assert.java:126)	at org.junit.Assert.assertEquals(Assert.java:145)	at org.kuali.kits.kms.repository.test.BatchProcessorTest.testAsikLocking(BatchProcessorTest.java:90)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)	at java.lang.reflect.Method.invoke(Method.java:597)