upgrading Gateway 9.3 to 10 and getting Hazelcast related clustering issues upon startup.
This is a known issue and the workaround is documented in Article #145139
by removing this two Hazelcast assertions :
a) EmbeddedHazelcastSharedStateProviderAssertion-1.0.00.aar
b) ExternalHazelcastSharedStateProviderAssertion-1.0.00.aar
per indicated in https://knowledge.broadcom.com/external/article?articleId=145139
if we have "OTK Cache Store" assertion to store and read some data from in-memroy cache.
Does the Hazelcast extention will have any dependceny with these assertions/in-memory cache?
Release : 10.0
Component : API GATEWAY
There is no impact , OTK Cache store ENCAS uses node-level cache assertions.
ENCAS: Encapsulated Assertions
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/9-4/policy-assertions/assertion-palette/service-availability-assertions/store-to-cache-assertion.html
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-management-oauth-toolkit/4-3/apis-and-assertions/encapsulated-assertions.html