PdxRegistryMismatchException when WAN is trying to replicate the data

Products

• VMware Tanzu Gemfire

Issue/Introduction

When Gateways are trying to replicate the data between two sites or clusters, replication fails may fail with a PdxRegistryMismatchException exception. Entire stack trace is as follows:

Caused by: com.gemstone.gemfire.pdx.PdxRegistryMismatchException: Trying to add a PDXType with the same id as an existing PDX type. id=117440513, existing pdx type PdxType[dsid=7,typenum=1,name=__GEMFIRE_JSON,fields=[owner:String:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1, version:String:1:1:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=1, ]], new type PdxType[dsid=7,typenum=1,name=__GEMFIRE_JSON,fields=[links:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1, id:String:1:1:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=1, meta:Object:2:2:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=2, revision:byte:3:2:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=3, createdBy:String:4:3:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=3, createdDate:String:5:4:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=4, modifiedBy:String:6:5:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=5, name:String:7:6:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=6, mediaCategory:String:8:7:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=7, displayName:String:9:8:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=8, modifiedDate:String:10:9:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=9, ]]
at com.gemstone.gemfire.pdx.internal.PeerTypeRegistration$2.beforeUpdate(PeerTypeRegistration.java:169)
at com.gemstone.gemfire.internal.cache.SearchLoadAndWriteProcessor.doLocalWrite(SearchLoadAndWriteProcessor.java:865)
at com.gemstone.gemfire.internal.cache.SearchLoadAndWriteProcessor.doNetWrite(SearchLoadAndWriteProcessor.java:208)
at com.gemstone.gemfire.internal.cache.DistributedRegion.cacheWriteBeforePut(DistributedRegion.java:2839)
at com.gemstone.gemfire.internal.cache.AbstractRegionMap.invokeCacheWriter(AbstractRegionMap.java:3215)
at com.gemstone.gemfire.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2979)
at com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5838)
at com.gemstone.gemfire.internal.cache.DistributedRegion.virtualPut(DistributedRegion.java:386)
at com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:118)
at com.gemstone.gemfire.internal.cache.LocalRegion.basicUpdate(LocalRegion.java:5813)
at com.gemstone.gemfire.internal.cache.LocalRegion.basicBridgePut(LocalRegion.java:5445)
at com.gemstone.gemfire.internal.cache.tier.sockets.command.GatewayReceiverCommand.cmdExecute(GatewayReceiverCommand.java:427)
at com.gemstone.gemfire.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:181)
at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:799)
at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:930)
at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1179)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:555)
at java.lang.Thread.run(Thread.java:745)

Environment

Product Version: 9.0

Resolution

This exception occurs when pdx metadata differs in the Sender site and the Receiver site. To overcome this issue, please follow these steps:

• Clean the data on the receiver side and push the data again from sender site so that the pdx metadata gets build up again on the receiver side.
• Make sure the you set the distribution-id for both of the sites (Senders and Receivers).