When a second cache server is started for the same cache cluster an error is thrown.

When a second cache server is started for the same cache cluster an error is thrown.

book

Article ID: KB0089548

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
Description:
==========
When a second cache server is started for the same cache cluster an error is thrown such as:
(Wrapped: CacheName=repl-unlimited$dist-XXXXXXXX$$Master, Key=-3)
[main] - java.io.InvalidClassException: com.tibco.cep.runtime.service.om.coherence.cluster.CacheClusterConfiguration; local class incompatible: stream classdesc serialVersionUID = 439766165056522215, local class serialVersionUID = -4669280368576009747

Environment:
==========
All

Symptoms:
=========
Note, you can start either of two cache servers but which ever one you start the second will fail with the above error.

Cause:
=====
The cluster software is complaining that the member joining does not have the same schema or classes to the cluster that is running.

Resolution:
=========
Turn on Coherence logging as necessary.  This error can be caused by starting up Business Event(BE) cache server with a different set of BE hotfixes.

Issue/Introduction

When a second cache server is started for the same cache cluster an error is thrown.