Startup Error while deploying external hazelcast in 883 version

General
, , , , ,
1

Hazelcast startup is interrupted while deploying external hazelcast on 883 version in client managed cloud on k8s, statefulset is created but the first pod fails to come up clean. Logs on the pods indicate an issue with a config file, please see below.

Am using the latest docker image for clustering-service:1.3.15.

Has anyone encountered such issue before? Appreciate any insights on this one. Thanks in advance.

Apr 19, 2024 10:02:55 PM com.pega.hazelcast.v5.internal.config.AbstractConfigLocator
INFO: Loading configuration ‘/opt/hazelcast/customconfig/hazelcast.xml’ from System property ‘hazelcast.config’
Apr 19, 2024 10:02:55 PM com.pega.hazelcast.v5.internal.config.AbstractConfigLocator
INFO: Using configuration file at /opt/hazelcast/customconfig/hazelcast.xml
[Fatal Error] :96:66: The reference to entity “t1” must end with the ‘;’ delimiter.
Apr 19, 2024 10:02:55 PM com.pega.hazelcast.v5.config.XmlConfigBuilder
SEVERE: Failed to parse /opt/hazelcast/customconfig/hazelcast.xml
Exception: The reference to entity “t1” must end with the ‘;’ delimiter.
Hazelcast startup interrupted.
The reference to entity “t1” must end with the ‘;’ delimiter.

2

@shushruthR

The error message you’re seeing indicates that there’s a problem with the XML configuration file for Hazelcast. The error message “The reference to entity ‘t1’ must end with the ‘;’ delimiter” suggests that there’s a syntax error in the XML file. This could be caused by a missing semicolon (:wink: at the end of an entity reference.

You should check the ‘hazelcast.xml’ file located at ‘/opt/hazelcast/customconfig/’ and ensure that all entity references are correctly formatted. An entity reference in XML starts with an ampersand (&) and ends with a semicolon (;). If any entity references are missing a semicolon, this could cause the error you’re seeing.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

Updating external Hazelcast on Kubernetes