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.

  2. ,

    My guess is there is some kind of static state in the code being tested or in the test itself, so the tests aren't isolated. Adding the test changes the test order. In any case, your best course of action is to use the debugger to see why the tests fail.

Solutions on the web

via GitHub by hasancelik
, 1 year ago
Near cache owned entry count should be > 400 but was 66
via GitHub by hasancelik
, 1 year ago
Near cache owned entry count should be > 400 but was 277
via GitHub by hasancelik
, 1 year ago
Near cache hits should be > 400 but were 371
via GitHub by hasancelik
, 2 years ago
ownedEntryCount should be smaller than 100, but was 100
via Oracle Community by WillyM, 1 year ago
via GitHub by elharo
, 1 year ago
Project should be faceted
java.lang.AssertionError: Near cache owned entry count should be > 400 but was 66	at org.junit.Assert.fail(Assert.java:88)	at org.junit.Assert.assertTrue(Assert.java:41)	at com.hazelcast.map.nearcache.NearCacheTest.testGetAsyncPopulatesNearCache(NearCacheTest.java:554)