Question
Accenture
IN
Last activity: 16 Oct 2018 12:03 EDT
AES Push log usage data agents is getting failed with same exception..
Exception at 20170823T161948.290 GMT: com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!
Exception at 20170823T161948.290 GMT: com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active! at com.hazelcast.spi.AbstractDistributedObject.throwNotActiveException(AbstractDistributedObject.java:81) at com.hazelcast.spi.AbstractDistributedObject.lifecycleCheck(AbstractDistributedObject.java:76) at com.hazelcast.spi.AbstractDistributedObject.getNodeEngine(AbstractDistributedObject.java:70) at com.hazelcast.topic.impl.TopicProxy.publish(TopicProxy.java:33) at com.pega.pegarules.cluster.internal.PRClusterHazelcastImpl.broadcastSystemPulse(PRClusterHazelcastImpl.java:254) at com.pega.pegarules.data.internal.access.DatabaseImpl.attemptToProcessUpdates(DatabaseImpl.java:2730) at com.pega.pegarules.data.internal.access.DatabaseImpl.processUpdates(DatabaseImpl.java:2322) at com.pega.pegarules.data.internal.access.Saver.save(Saver.java:651) at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:5108) at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:5094) at com.pegarules.generated.activity.ra_action_pushlogusagedata_5b19b97cae0347247e60446a7287f691.step26_circum0(ra_action_pushlogusagedata_5b19b97cae0347247e60446a7287f691.java:2071) at com.pegarules.generated.activity.ra_action_pushlogusagedata_5b19b97cae0347247e60446a7287f691.perform(ra_action_pushlogusagedata_5b19b97cae0347247e60446a7287f691.java:549) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3505) at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:721) at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:602) at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:945) at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1259) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1008) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:901) at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:670) at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991) at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532) at java.lang.Thread.run(Thread.java:745)
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
US
this is a core platform issue more so than anything to do with AES. The pushLogUsage agent updates a dynamic system setting. Dynamic system settings changes must be 'pulsed' to other nodes. The pulse is implemented by sending a message via hazelcast. It appears that hazelcast has failed, hence the push fails, hence the pushLogUsage agent can't update the DSS, hence the agent fails.
As pulse/hazelcast is necessary to ensure that any rule change, system settings change or node level delcarative page changes are shared across the cluster, hazelcast errors should be investigated and remediated quickly. On older systems, hazelcast errors were often from old nodes with inaccurate information in pr_sys_statusnodes table so the simple solution was to down system, truncate table and restart.
There are cluster/hazelcast log files on all nodes. Open a support ticket and provide pegarules log files from the node with error and cluster/hazelcast log files on all nodes.
Accenture
IN
We have restarted the Server several times,but we still have the issue. Could you please let me know what causes this issue for the agent getting stopped.
Infosys limited
IN
Hi All,
Am also facing the same issue in my application, can any one know why it will happen and also have any solution for this issue. Thanks in advance
kalyan
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.
Accepted Solution
Pegasystems Inc.
US
this is a core platform issue more so than anything to do with AES. The pushLogUsage agent updates a dynamic system setting. Dynamic system settings changes must be 'pulsed' to other nodes. The pulse is implemented by sending a message via hazelcast. It appears that hazelcast has failed, hence the push fails, hence the pushLogUsage agent can't update the DSS, hence the agent fails.
As pulse/hazelcast is necessary to ensure that any rule change, system settings change or node level delcarative page changes are shared across the cluster, hazelcast errors should be investigated and remediated quickly. On older systems, hazelcast errors were often from old nodes with inaccurate information in pr_sys_statusnodes table so the simple solution was to down system, truncate table and restart.
There are cluster/hazelcast log files on all nodes. Open a support ticket and provide pegarules log files from the node with error and cluster/hazelcast log files on all nodes.