Troubleshooting
Problem
Replication domain members are not listed via WebSphere Integrated Solutions Console or wsadmin commands
Symptom
Replication Domain members are either not present or not listed correctly.
Cause
There is at least one corrupted server.xml in the environment which may or may not belong to the members missing from the Replication domain members list.
Diagnosing The Problem
Replication domain members are missing or none are listed in the WebSphere Integrated Solutions Console or wsadmin commands
Using the trace string for domain replication service (DRS) issues
*=info:com.ibm.ws.drs.*=all
The following log entry will appear.
DRSCommandPro E listServerReferencesToDRD - Exception:
The corrupted sever.xml may be missing the messageBrokerDomainName entry, and look like this:
<sessionDRSPersistence xmi:id="DRSSettings_1332392397069"/>
A complete and correct entry should look like this:
<sessionDRSPersistence xmi:id="DRSSettings_1332392397069" messageBrokerDomainName="MyRepDomain"/>
or
<cacheReplication xmi:id="DRSSettings_1374081521699" messageBrokerDomainName="MyRepDomain"/>
Resolving The Problem
APAR IBM PM34329: CONSOLE DOESN'T HANDLE MISSING MESSAGEBROKERDOMAINNAME ON SESSIONDRSPERSISTENCE ATTRIBUTE
http://www-01.ibm.com/support/docview.wss?uid=swg1PM34329
has been created to address the issue and is included in WebSphere Application Server Fix Pack 7.0.0.19 and 8.0.0.1 and on. Please ensure you are at that Fix Pack level or higher.
While the APAR fixes the code that corrupted the server.xml and prevents further corruption there is nothing to fix the server.xml once it is corrupted.
The options are to either
1) find the corrupted server.xml and fix it manually
IMPORTANT: To fix this manually it is necessary to review each and every server.xml in the entire environment to ensure all needed entries are listed correctly
2) regenerate all the server.xml DRS configuration entries
The server.xml entries can be rebuilt by modifying the Session Management Distributed environment settings to the desired setting (None, Memory-to-memory or database), then save and manually synchronize that change to all the nodes.
To verify that cache replication is configured and working, look for entries like these in SystemOut.log:
DYNA1001I: WebSphere Dynamic Cache instance named MyCache initialized successfully.
CWWDR0001I: Replication instance launched : MyCache .
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21646243