Abaondoned thread causing slow index performance in Coherence 3.5.3 and 3.6 (Doc ID 1260694.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Coherence - Version: 3.5.3 to 3.6.0 - Release: AS10g to AS10g
Information in this document applies to any platform.

Symptoms

Errors like the following are thrown in Coherence 3.5.3 and/or 3.6 :

####<Oct 15, 2010 10:02:30 PM PDT> <SEVERE> <Coherence> <gsjcache01> <9003> <Jdk.log: 3.5.3/465p7 (thread=Abandon, member=10): A worker thread "base-partitionedWorker:3 executing task "PutJob{CacheId=282762179422007, Partition=212}", did not respond to 8 interrupt requests. The execution was canceled. The thread is abandoned...
at com.tangosol.util.SimpleMapIndex.insert(SimpleMapIndex.java:125)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$Storage.updateIndex(DistributedCache.CDB:19)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$Storage.postInvoke(DistributedCache.CDB:8)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$Storage.put(DistributedCache.CDB:156)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onPutAllRequest(DistributedCache.CDB:35)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$PutAllRequest$PutJob.run(DistributedCache.CDB:2)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:1)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:63)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms