Support Article
BIX node is invisible in SMA
Summary
Business Intelligence Exchange (BIX) node is invisible in the System Management Application (SMA).
Error Messages
438 [c-operation.thread-3] [ STANDARD] [ ] [ ] (hazelcast.spi.OperationService) FATAL - [96500782c07d02f6d0a297105684b96b] GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
at com.hazelcast.nio.serialization.ByteArrayInputOutputFactory.createInput(ByteArrayInputOutputFactory.java:34)
at com.hazelcast.nio.serialization.SerializationServiceImpl.createObjectDataInput(SerializationServiceImpl.java:436)
at com.hazelcast.nio.serialization.StreamSerializerAdapter.toObject(StreamSerializerAdapter.java:63)
456 [erClockSynchDaemon-0] [STANDARD] [ ] [ ] (nternal.PRClusterHazelcastImpl) ERROR - java.util.concurrent.ExecutionException: com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!
458 [PegaRULES-Batch-43] [STANDARD] [ ] [PegaRULES] (nternal.async.AgentInfoManager) ERROR- Failed to set agentInfo for agent systemeventevaluation defined on ruleset pega-eventprocessing for the node bix_i-0f088be31172c39b3
com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!
at com.hazelcast.spi.impl.BasicOperationService.shutdown(BasicOperationService.java:441)
at com.hazelcast.spi.impl.NodeEngineImpl.shutdown(NodeEngineImpl.java:390)
at com.hazelcast.instance.Node.shutdown(Node.java:407)
Steps to Reproduce
Unknown
Root Cause
A defect or configuration issue in the operating environment. The out of memory exceptions cause the Hazelcast to become inactive and as a result the node goes off the cluster.
Resolution
Perform the following local-change:
- Check if there is a memory leak
- Increase the heap size in the system
Proper analysis of heap dumps and Garbage Collection (GC) logs must be done. In the System Management Application auto discovery, details of the nodes which are present in the cluster is fetched. As this node is not in the cluster, the System Management Application is unable to read the node information.
Published August 15, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.