Splitting A 4 Nodes Cluster Into Two 2 Nodes Clusters Provokes Error In EDR Generation
(Doc ID 2482703.1)
Last updated on AUGUST 24, 2020
Applies to:
Oracle Communications Services Gatekeeper - Version 6.1.0 and laterInformation in this document applies to any platform.
Symptoms
See EDR Generation issue when splitting a 4 node cluster (Server1, Server2, Server3, Server4) into two smaller clusters with 2 nodes each Server1 + Server2 and Server3 + Server4.
The splitting was done as follows:
Cluster1
Name: WLNG_Cluster
Nodes: IP_Server1:PORT_Server1, IP_Server2:PORT_Server2
Cluster2
Name:WLNG_Cluster_Second
Nodes: IP_Server3:PORT_Server3, IP_Server4:PORT_Server4
Both clusters belong to the same Coherence Cluster: WLNG_Coherence_Cluster
By Default the HA-Domain creates the JMS-modules:
WLNGEDRResource
WLNGJMSResource
WLNG_ATJMSResource
Added the corresponding modules for the new cluster:
Second_WLNGEDRResource
Second_WLNGJMSResource
Second_WLNG_ATJMSResource
The issue is that the EDRs are not generated for requests that reach Server3 and Server4 .
For each request to Server 3 or 4 the following error is observed:
Checking the JNDI tree of each server and it can be seen that for Server1 and Server2 the object com.bea.wlcp.wlng.edr.at.atEdrLog is present whereas for Server3 and Server4 it isn't.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |