org.jsr107.tck.management.CacheMBStatisticsBeanTest.testPutIfAbsent()

[timeck]

This test asserts that neither the "hit" or "miss" counts are affected by two Cache.putIfAbsent() operations

The spec lists this however (page 131):

operation	Puts	Removals	Hits	Misses
boolean putIfAbsent(K key, V value)	Yes	No	Yes	Yes

I am of the opinion that the first putIfAbsent() would count as both a "put" and a "miss", and the second call would record a "hit" in the cache statistics

[gregrluck]

Yes you are correct. This change will break all of the existing implementations who have all followed the incorrect test and the incorrect RI.

We are therefore setting this 1.1.0 of the TCK which under the rules is not mandatory for 1.0 implementations. See the TCK Users Guide.

[gregrluck]

Moving this to 1.0.1. Implementations will have to fix their behaviour.