I've looked over the thread dumps here and I see no evidence of any kind of deadlock occurring in the product. I do see that you are using explicit locking on the cache - one thing that could cause this issue would be if there were unbalanced lock/unlock calls through the explicit locking API. It would be likely be worth your while to double check all of your code that interacts with the explicit locking API to confirm that there are no errors there.
Also, if you are a paying customer and have a support contract with us, it would definitely be best to pursue this through the regular support channels.
Thanks for your reply.
Some time ago, we didn't using explicit lock, and had the problem.
Then we add the explicit locking, Code:
ele = cache.get(key);
Other I feel confused that why the put/get cache is blocking at AbstractLockedOffHeapHashMap?
Who hold the lock in the AbstractLockedOffHeapHashMap and not release?