Support Article
Lot of ADMException seen during ADM node restart.
SA-30144
Summary
Lots of ADMException thrown when Adaptive Decision Manager (ADM) node is restarted.
Error Messages
2016-10-12 11:15:26,376 [b5f.cached.thread-25] [ STANDARD] [ ] [ ] ( adm.client.ADMException) ERROR - Exception occurred within ADM with message: Server is not in RUNNING state
com.pega.decision.adm.client.ADMException: Server is not in RUNNING state
at com.pega.decision.adm.client.ADMException.raise(ADMException.java:39)
at com.pega.decision.adm.server.ServerImpl.serviceCall(ServerImpl.java:717)
at com.pega.decision.adm.server.ServerImpl.getModelUpdates(ServerImpl.java:617)
at com.pega.decision.adm.service.MessageHandler$23.apply(MessageHandler.java:284)
at com.pega.decision.adm.service.MessageHandler$23.apply(MessageHandler.java:279)
at com.pega.decision.adm.service.MessageBinder.handle(MessageBinder.java:53)
at com.pega.decision.adm.service.MessageHandler.handle(MessageHandler.java:384)
at com.pega.decision.adm.service.MessageHandler.handleMessage(MessageHandler.java:28)
at com.pega.decision.adm.service.ADMCallableMessage.call(ADMCallableMessage.java:27)
at com.pega.decision.adm.service.ADMCallableMessage.call(ADMCallableMessage.java:10)
at com.pega.dsm.dnode.api.prpc.service.AbstractDsmService.handleMessageInternal(AbstractDsmService.java:229)
at com.pega.dsm.dnode.impl.prpc.service.ServiceDeploymentImpl$PostMessageJobData.handleMessage(ServiceDeploymentImpl.java:354)
at com.pega.dsm.dnode.impl.prpc.service.ServiceDeploymentImpl$PostMessageJob.execute(ServiceDeploymentImpl.java:324)
at com.pega.dsm.dnode.impl.prpc.service.ServiceDeploymentImpl$PostMessageJob.execute(ServiceDeploymentImpl.java:321)
at com.pega.pegarules.cluster.internal.PRPCTask.call(PRPCTask.java:110)
at com.pega.pegarules.cluster.internal.PRPCTask.call(PRPCTask.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at com.hazelcast.executor.impl.DistributedExecutorService$CallableProcessor.run(DistributedExecutorService.java:187)
at com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.run(CachedExecutorServiceDelegate.java:209)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:76)
at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:92)
Steps to Reproduce
On a multinode environment, restart a ADM node, while other nodes are up.
Root Cause
A defect in Pegasystems’ code or rules. JMS messages are being consumed, before the ADM server is started completely.
Resolution
Apply HFix-29971.
Published November 17, 2016 - 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.