Support Article
Visual Business Director node fails with a Hazlecast error
Summary
The Visual Business Director (VBD) node is unstable and affects the Marketing campaign.
Error Messages
841[fault(self-tuning)'][STANDARD][][](ernal.async.BatchRequestorTask)ERROR - Batch activity "System-Queue-GenericWaitFlow.ResumeGenericFlow" threw:
hazelcast.core.HazelcastInstanceNotActiveException:Hazelcast instance is not active!
at hazelcast.spi.impl.operationservice.impl.InvocationRegistry.shutdown(InvocationRegistry.java:192)~[hazelcast-3.8_1.jar:3.8]
at hazelcast.spi.impl.operationservice.impl.OperationServiceImpl.shutdownInvocations(OperationServiceImpl.java:479) ~[hazelcast-3.8_1.jar:3.8]
at hazelcast.spi.impl.NodeEngineImpl.shutdown(NodeEngineImpl.java:487)~[hazelcast-3.8_1.jar:3.8]
at hazelcast.instance.Node.shutdownServices(Node.java:489) ~[hazelcast-3.8_1.jar:3.8]
at hazelcast.instance.Node.shutdown(Node.java:463)~[hazelcast-3.8_1.jar:3.8]
at hazelcast.instance.OutOfMemoryHandlerHelper.tryShutdown(OutOfMemoryHandlerHelper.java:61)~[hazelcast-3.8_1.jar:3.8]
at hazelcast.instance.DefaultOutOfMemoryHandler.onOutOfMemory(DefaultOutOfMemoryHandler.java:87)~[hazelcast-3.8_1.jar:3.8]
at hazelcast.instance.OutOfMemoryErrorDispatcher.onOutOfMemory(OutOfMemoryErrorDispatcher.java:189) ~[hazelcast-3.8_1.jar:3.8]
at hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:94)~[hazelcast-3.8_1.jar:3.8]
Steps to Reproduce
- Install Pega Marketing 7.3 on Pega 7.3.1
- Create a few agents to fulfil the application requirements
Root Cause
A defect or configuration issue in the Operating environment. Memory issue with the VBD node.
Resolution
Perform the following local-change:Increase the JVM Heapsize of the VBD node.
Published October 10, 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.