Coherence Error Stopping The Cluster Service Which Causing Production Batch Failures In RMB
(Doc ID 2723971.1)
Last updated on DECEMBER 18, 2023
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 2.4.0.0.0 and laterInformation in this document applies to any platform.
Goal
RMB Batch is failing in Production Environment due to the below coherence error from the Batch server.
- 2020-10-15 09:59:22,283 [Logger@9254070 12.1.3.0.0] ERROR (Coherence) 2020-10-15 09:59:22.282/2347.415 Oracle Coherence GE 12.1.3.0.0 (thread=Cluster, member=5): Received cluster heartbeat from the senior Member(Id=12, Timestamp=2020-10-14 22:32:03.759, Address=10.219.149.147:8088, MachineId=47939, Location=site:,machine:lad1wdahp2004,process:32043, Role=OUAF_Base_TPW) that does not contain this Member(Id=5, Timestamp=2020-10-15 09:20:49.515, Address=10.220.28.185:20200, MachineId=55123, Location=site:,machine:lad1rmbhp2001,process:8054, Role=OUAF_Base_TPW); stopping cluster service.
- 2020-10-15 09:59:22,815 [Logger@9254070 12.1.3.0.0] ERROR (Coherence) 2020-10-15 09:59:22.811/2347.944 Oracle Coherence GE 12.1.3.0.0 (thread=Cluster, member=5): Full Thread Dump:
"UCP-worker-thread-24" id=204 State:WAITING
at sun.misc.Unsafe.park(Native Method)
- waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@acc9991
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:957)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:917)
at java.lang.Thread.run(Thread.java:662)
What is the cause of this?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |