Coherence Federation Worker Threads do not have the Service Name and their Function Description in their Thread Name.

(Doc ID 2389355.1)

Last updated on MAY 03, 2018

Applies to:

Oracle Coherence - Version 12.2.1.0.0 to 12.2.1.3.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

A customer has reported that in the federated coherence clusters on an issue taking the thread dumps not helping much to differentiate the threads of different participants of the federation cache schemes. The DestinationController worker thread has a generic name of "Worker:0".  Seeing as there is an up to n x m mapping of DestinationController workers (where n is the number of federation services and m is the number of remote participants) it can be difficult to track activity for a specific controller.

 

Changes

 

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