Upgrade Error 9.3 to 9.4

book

Article ID: 192257

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

After upgrading gateway from 9.3CR5 to 9.4 CR4 I am getting below error on starting to gateway !

2020-06-02T16:14:21.176+0300 WARNING 1 com.l7tech.server.boot.GatewayMain: Error starting server : Lifecycle error: Could not initialize Hazelcast cluster
com.l7tech.server.LifecycleException: Lifecycle error: Could not initialize Hazelcast cluster
        at com.l7tech.server.LifecycleExtensionComponent.start(Unknown Source)
      
        at com.l7tech.server.boot.GatewayMain.main(Unknown Source)
Caused by: com.ca.apim.gateway.extension.lifecycle.LifecycleException: Could not initialize Hazelcast cluster
        at com.l7tech.external.assertions.hazelcastembeddedprovider.server.a.start(Unknown Source)
        ... 6 more
Caused by: org.springframework.dao.IncorrectResultSizeDataAccessException: query did not return a unique result: 2
        at org.springframework.orm.hibernate3.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:669)
        at org.springframework.orm.hibernate3.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:412)
   

**** Unable to start the server: Error starting server : Lifecycle error: Could not initialize Hazelcast cluster

Environment

Release : 9.4

Component : API GATEWAY

Resolution

This could be caused by a duplicate firewall rule in the database for the hazelcast port 8777 

Which is causing the error :

Caused by: org.springframework.dao.IncorrectResultSizeDataAccessException: query did not return a unique result: 2

To check this open  policymanager , go to listen ports and select firewall rules

Check if there is a duplicate entry for port 8777 .

If this is the case remove one of them .

After that try to restart ssg and see if the error  message is gone in the ssg logs.

Attachments