The API, though I am not a fan of the RI for one reason. It is the first JSR RI that I am aware of where the authors advice against using, it is unsupported, and intentionally low quality. All other RIs that I know of were production grade quality to ensure it met user's needs. This one was to pass a specification requirement.
- The API violates many of Josh Bloch's guidances [1], including items in Effective Java.
- Many of its features are incompatible with itself. For example, the AOP support cannot be used with loaders, writers, or listeners.
- The AOP support does not support atomic memoization (dog piling [2]) and can crash if initializing the same cache concurrently.
- The JavaDoc dictates implementation details that matched the lead's product, rather than being open ended to allow alternative algorithmic choices.
- The JSR defines an configuration API that is not suitable for production use and promotes the silent usage of unbounded anonymous caches.
- The interfaces do not attempt to feel natural alongside the Java's Collection Framework nor the direction that the language has been heading. It redefines terms, like "access", in an incompatible way.
- Despite numerous delays in being accepted, the JSR was not modified to take advantage of significant changes in the language (java.time, lambdas, CompletableFuture, etc).
- The TCK is not robust, does not check concurrency, and bugs in it languished.
- Most importantly, writing code using JCache is not enjoyable and it is often not flexible enough to solve most needs.
There are likely many more, but that is a short list that comes to mind in a few minutes.
[1] https://www.infoq.com/articles/API-Design-Joshua-Bloch
[2] https://en.wikipedia.org/wiki/Cache_stampede