Can we disable DSM and its related services if our apps are not using it
We are seeing in logs like below messages
" Waiting for node to become usable before starting DSM Services"
This is on Pega 7.3.1/CRM 7.3.1
Our apps dont use DSM
Navy Federal Credit Union
US
Pega 7.3.1 comes all the DSM rulesets along with PegaRULES • 07.10 application stack. We cannot bypass those rulesets.
However, if your application does not use that feature, these rules will not be loaded to Assembler, JVM heap memory.
Though you see them in your application stack this will not cause any performance issues as long as you don't invoke PegaDecisioning rules.
PayPal
US
There are entries in JVM startup like below;
There are entries in JVM startup like below;
2018-06-02 16:16:01,672 ( prpc.service.ServiceManager) INFO - Waiting for node to become usable before starting DSM Services
2018-06-02 16:17:01,792 ( prpc.service.ServiceManager) INFO - Waiting for node to become usable before starting DSM Services
2018-06-02 16:18:01,907 ( prpc.service.ServiceManager) INFO - Waiting for node to become usable before starting DSM Services
2018-06-02 16:19:02,013 ( prpc.service.ServiceManager) INFO - Waiting for node to become usable before starting DSM Services
2018-06-02 16:20:02,128 ( prpc.service.ServiceManager) INFO - Waiting for node to become usable before starting DSM Services
2018-06-02 16:20:26,604 (dictionary.ConclusionCacheImpl) INFO - Starting conclusion pre-load...
2018-06-02 16:21:02,246 ( prpc.service.ServiceManager) INFO - Waiting for node to become usable before starting DSM Services
2018-06-02 16:21:47,103 (dictionary.ConclusionCacheImpl) INFO - Pre-Loaded 76430 conclusions
2018-06-02 16:21:47,104 ( external.async.IStartupTask) INFO - load pegaConclusions ..done
2018-06-02 16:21:47,112 ( external.async.IStartupTask) INFO - load global declarative classes ..starting
2018-06-02 16:21:47,113 (bi.DeclarativeCacheManagerImpl) INFO - Starting global declarative cache pre-load...
2018-06-02 16:22:02,471 ( prpc.service.ServiceManager) INFO - Waiting for node to become usable before starting DSM Services
2018-06-02 16:23:03,061 ( prpc.service.ServiceManager) INFO - Waiting for node to become usable before starting DSM Services
Each of "Waiting for node to become usable before starting DSM Services" is taking ~1 minute, are those not delaying JVM startup?
Updated: 11 Jun 2018 18:36 EDT
Pegasystems Inc.
US
Make sure you have not commissioned nodes for any of the DSM services. If you see any nodes under any of these four tabs, decom the node. If you do not see any, let us know.
Aaseya IT Solutions
IN
Also, make sure OOTB agents are disabled if any. Are you using CS framework?
You might look at disabling NBA to disable hitting next best action.