Question
Independent
CA
Last activity: 11 Dec 2025 9:10 EST
Pega 25 Single Node Container - Admin Studio shows no node is running
Up to Pega 24.2, for PoC purposes, I was able to create a single Docker container (NODE_TYPE=WebUser,BackgroundProcessing,Search) Pega node while externalizing Kafka and SRS. I used the same "recipe" for Pega 25, the node came up successfully. I am able to log in, navigate Dev / App studios etc. However, there's one issue.
When I used Admin Studio to list the nodes, I got ZERO nodes running. Admin studio did not list the node that I have logged into.
In the PegaRULE.log file, I saw this:
Up to Pega 24.2, for PoC purposes, I was able to create a single Docker container (NODE_TYPE=WebUser,BackgroundProcessing,Search) Pega node while externalizing Kafka and SRS. I used the same "recipe" for Pega 25, the node came up successfully. I am able to log in, navigate Dev / App studios etc. However, there's one issue.
When I used Admin Studio to list the nodes, I got ZERO nodes running. Admin studio did not list the node that I have logged into.
In the PegaRULE.log file, I saw this:
2025-12-11 04:54:35,011 [ AsyncServices-5] [ STANDARD] [ shared] [ Verify:01.01.01] (rationsDistributedExecutorImpl) ERROR author@verify - Caught exception while getting result from future object
java.util.concurrent.ExecutionException: com.pega.platform.remoteexecution.management.UnresponsiveNodeException: Remote execution request 9fe00bbd-02bb-4533-b6dc-e429dafea629 was not acknowledged by node 6100dd74-1fdf-4caa-814b-fa88cb372cbe within the timeout
at com.pega.platform.remoteexecution.ResponseMessage.getResponse(ResponseMessage.java:60)
at com.pega.platform.remoteexecution.internal.ResponseFuture.get(ResponseFuture.java:84)
at com.pega.platform.remoteexecution.internal.ResponseFuture.get(ResponseFuture.java:23)
at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:75)
at com.pega.pegarules.management.internal.system.operations.SystemOperationsDistributedExecutorImpl.createResultFromOneFutureObject(SystemOperationsDistributedExecutorImpl.java:249)
at com.pega.pegarules.management.internal.system.operations.SystemOperationsDistributedExecutorImpl.collectDoneResults(SystemOperationsDistributedExecutorImpl.java:237)
at com.pega.pegarules.management.internal.system.operations.SystemOperationsDistributedExecutorImpl.getResultsFromFutureObjects(SystemOperationsDistributedExecutorImpl.java:197)
at java.base/java.util.Optional.map(Optional.java:260)
at com.pega.pegarules.management.internal.system.operations.SystemOperationsDistributedExecutorImpl.executeOnAllNodesInCluster(SystemOperationsDistributedExecutorImpl.java:102)
at com.pega.pegarules.management.internal.system.operations.AbstractManagementAPI.executeOnAllNodes(AbstractManagementAPI.java:195)
at com.pega.pegarules.management.internal.system.operations.ClusterManagementAPI.getNodesInCluster(ClusterManagementAPI.java:714)
at com.pegarules.generated.activity.ra_action_pzgetnodesincluster_fea19cc7f900010c93054d4b0f950a2e.step1_circum0(ra_action_pzgetnodesincluster_fea19cc7f900010c93054d4b0f950a2e.java:165)
at com.pegarules.generated.activity.ra_action_pzgetnodesincluster_fea19cc7f900010c93054d4b0f950a2e.perform(ra_action_pzgetnodesincluster_fea19cc7f900010c93054d4b0f950a2e.java:76)
Upon more investigation, I have isolated the line of Java code that gives the exception is as follows:
Map<String, String> clusterInfo = pega.getSystemOperationsProvider().getClusterManagementAPI().getClusterInformation();
It's my understanding that Pega 25 no longer makes use of Hazelcast. My question is, what additional environment variables are required to pass in a Pega 25+ container in order to resolve the problem that I outlined above?