APAR status
Closed as program error.
Error description
Starting a catalog service endpoint in a different catalog service domain creates an exception similar to the following example: CatalogEndpoi E CWOBJ7401E: A discrepancy in the catalogServiceEndPoints value was detected. The catalogServiceEndPoints value must be the same on each catalog server. This server (USRTPCSD\USRTPCSDASA02\QR10USRTPA02) will be stopped. Exception detected: java.lang.IllegalStateException: Value of "catalogServiceEndPoints" property/argument must be consistent across catalog servers. USRTPCSD\USRTPCSDASA02\QR10USRTPA02 (this server) = USRTPCSD\USRTPCSDASA01\QR10USRTPA01:USRTPCSDASA01.rtp.raleigh.ib m.com: 30566:0:30547,USRTPCSD\USRTPCSDASA02\QR10USRTPA02:USRTPCSDASA02. rtp.raleigh.ibm.com:30566:0:30547, USRTPCSD\USRTPCSDASA02\UJ10GPECA02 = USRTPCSD\USRTPCSDASA01\UJ10GPECA01: USRTPCSDASA01.rtp.raleigh.ibm.com:30546:0:30527,USRTPCSD\USRTPCS DASA02\UJ10GPECA02: USRTPCSDASA02.rtp.raleigh.ibm.com:30546:0:30527 at com.ibm.ws.objectgrid.runtime.CatalogEndpointConsistency. onMessage(CatalogEndpointConsistency.java:197) at com.ibm.ws.hamanager.impl.HAGroupImpl.doOnMessage (HAGroupImpl.java:793) at com.ibm.ws.hamanager.impl.HAGroupImpl$HAGroupUserCallback. doCallback(HAGroupImpl.java:1359) at com.ibm.ws.hamanager.impl.Worker.run(Worker.java:64) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Local fix
Having different core groups for each catalog service domain works around the problem.
Problem summary
**************************************************************** * USERS AFFECTED: Users running multiple catalog service * * domains from eXtreme Scale inside of * * WebSphere Application Server. * **************************************************************** * PROBLEM DESCRIPTION: A discrepancy error occurs if the * * catalog service domain name and * * endpoints are not the same in all * * catalog service domains. * **************************************************************** * RECOMMENDATION: * **************************************************************** A check might prevent you from having multiple catalog server domains start with different endoints. However, this configuration is valid.
Problem conclusion
For the case of having different catalog service domain names, different endpoints can be configured. These servers will not be prevented from starting.
Temporary fix
Comments
APAR Information
APAR number
PM79536
Reported component name
WS EXTREME SCAL
Reported component ID
5724X6702
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-12-19
Closed date
2013-01-28
Last modified date
2013-01-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WS EXTREME SCAL
Fixed component ID
5724X6702
Applicable component levels
R850 PSY
UP
R860 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
28 January 2013