com.hazelcast.transaction.TransactionException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • com.hazelcast.transaction.TransactionException: Transaction couldn't obtain lock for the key: HeapData{type=-11, hashCode=-1899369607, partitionHash=-1899369607, totalSize=48, dataSize=40, heapCost=68} at com.hazelcast.map.impl.tx.TransactionalMapProxySupport.lockAndGet(TransactionalMapProxySupport.java:270)[hazelcast-3.6.4.jar:3.6.4] at com.hazelcast.map.impl.tx.TransactionalMapProxySupport.getForUpdateInternal(TransactionalMapProxySupport.java:117)[hazelcast-3.6.4.jar:3.6.4] at com.hazelcast.map.impl.tx.TransactionalMapProxy.getForUpdate(TransactionalMapProxy.java:124)[hazelcast-3.6.4.jar:3.6.4] at com.hazelcast.client.impl.protocol.task.transactionalmap.TransactionalMapGetForUpdateMessageTask.innerCall(TransactionalMapGetForUpdateMessageTask.java:43)[hazelcast-3.6.4.jar:3.6.4] at com.hazelcast.client.impl.protocol.task.AbstractTransactionalMessageTask.call(AbstractTransactionalMessageTask.java:34)[hazelcast-3.6.4.jar:3.6.4] at com.hazelcast.client.impl.protocol.task.AbstractCallableMessageTask.processMessage(AbstractCallableMessageTask.java:34)[hazelcast-3.6.4.jar:3.6.4] at com.hazelcast.client.impl.protocol.task.AbstractMessageTask.initializeAndProcessMessage(AbstractMessageTask.java:118)[hazelcast-3.6.4.jar:3.6.4] at com.hazelcast.client.impl.protocol.task.AbstractMessageTask.run(AbstractMessageTask.java:98)[hazelcast-3.6.4.jar:3.6.4] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_20] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_20] at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)[hazelcast-3.6.4.jar:3.6.4] at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:92)[hazelcast-3.6.4.jar:3.6.4]

Users with the same issue

Unknown visitor1 times, last one,