The first final release where this should have been fixed is 3.5.0, given the 3.5.0-Beta-2 Fix Version above.
NIZAR, your stack trace shows you are using ehcache as your second level cache provider, not JBoss Cache. This issue is for the JBC provider. Perhaps your issue is somehow similar, perhaps not. But the fix for this one was very specific to the JBC provider.
|