Upgrade HazelcastSerializationException Error from 9.x to 9.x or 10.x

book

Article ID: 145139

calendar_today

Updated On:

Products

CA API Gateway API SECURITY CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7) CA API Gateway Enterprise Service Manager (Layer 7) STARTER PACK-7 CA Microgateway

Issue/Introduction

Today after restart of upgraded node from 9.x to 9.x/10.x, we’re seeing below errors in both nodes of the cluster. How to fix it ?

2020-02-12T07:40:59.081+0000 SEVERE  122 com.hazelcast.spi.impl.operationexecutor.impl.OperationExecutorImpl: [xx.xx.xx.xx]:8777 [gateway] [3.10.2] Failed to process packet: Packet{partitionId=-1, conn=Connection[id=1, /xx.xx.xx.xx:13121->/xx.xx.xx.xx:8777, endpoint=[xx.xx.xx.xx]:8777, alive=true, type=MEMBER], rawFlags=10001, isUrgent=true, packetType=OPERATION, typeSpecificFlags=[isResponse=false, isOpControl=false]} on hz.gateway-hazelcast.priority-generic-operation.thread-0

com.hazelcast.nio.serialization.HazelcastSerializationException: Problem while reading DataSerializable, namespace: 0, ID: 0, class: 'com.hazelcast.cluster.impl.operations.JoinCheckOperation', exception: com.hazelcast.cluster.impl.operations.JoinCheckOperation

Environment

Release : 9.2

Component : API GTW ENTERPRISE MANAGER

Resolution

Disable Hazelcast Errors:

If Hazelcast is not available in your environment, the default MySQL will be used for in-memory storage and the performance may vary accordingly. In this case, if you do not want any Hazelcast assertions or extensions to be loaded, you can disable it completely with the following steps: 

1. Take a backup of the following assertion files in /opt/SecureSpan/Gateway/runtime/modules/assertions/ : 

a) EmbeddedHazelcastSharedStateProviderAssertion-1.0.00.aar 
b) ExternalHazelcastSharedStateProviderAssertion-1.0.00.aar 

2. Remove or move the assertion files to a location outside of the Gateway directory. 
3. Restart the ssg service. 

Upon restart, you should no longer see any Hazelcast related extensions being loaded in the ssg log. There also shouldn't be any Hazelcast thread observed in the thread dump.