Skip to main content
 
developerworks > Community >  Dashboard > WebSphere eXtreme Scale V6.1 User Guide > ... > ObjectGrid 6.1 cumulative fix 3 contents > Replica does not start or does not enter peer mode
developerWorks
Log In   View a printable version of the current page.
Overview New to Forums Wikis
Replica does not start or does not enter peer mode
Added by kristip, last edited by Chris.D.Johnson on Dec 18, 2007  (view change)
Labels: 
(None)

Getting Started Examples Reference API documentation
See the WebSphere eXtreme Scale Wiki for links to up-to-date eXtreme Scale Version 7.x documentation.

If you log in with your developerWorks ID, you can leave comments and feedback for the development team.

Component Catalog Services and Dynamic Environment
Software Version 6.1

Problem

Message CWOBJ1527 is logged or message CWOBJ1526 is missing from log.

This problem might happen for more than one reason. When a replica starts, the initialization message (CWOBJ1511) is logged, followed by a entering peer mode message (CWOBJ1526) which indicates that the replica successfully copied existing data and will receive current data from the primary. If the replica fails, one of the following situations occur:

  1. message CWOBJ1526 is missing from the log, or
  2. message CWOBJ1527 islogged, which indicates that the replica failed to enter peer mode.

For example:
CWOBJ9001W: This message is an English-only Warning message: Replica failed to enter peer mode. Reason: A transaction threw an error while copying data from the primary.
CWOBJ1527W: Replica accounting:mapSet1:0:payroll failed to enter peer mode after 0.03 seconds

Cause

The replica might have encountered a DuplicateKeyException exception while copying over existing data from the primary. Or it might have encountered a ClassCastException exception while copying over existing data from the primary. To confirm one of these errors, search the first failure data capture (FFDC) logs of the server with the failed replica for the following errors:

java.lang.ClassCastException
com.ibm.websphere.objectgrid.DuplicateKeyException

Workaround

Restart the server where the replica failed. The replica is placed elsewhere and might be able to start successfully.

Solution

Apply ObjectGrid cumulative intermediate fix 3.

Wiki Disclaimer and License
© Copyright IBM Corporation 2007,2010. All Rights Reserved.