Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Agents not running from PRUtils 'runagent' command-line option

SA-9801

Summary



Developer tries to run Agent using PRutils command line with 'runagent' argument and prpcutils.properties to specific Agent information. On running the 'runagent' PRUtils option, developer reported that Agent did not run. This was later verified in SMA by the user.

Following are the requirements shared by the developer:
a) Need to start the Agent from command-line.
b) Need to stop the Agent from command-line.
c) If we have 4 nodes, and want to start the Agent on the second node alone, then is there a way, one can specify the node name, node ID to start the agent in that node alone?

Error Messages



Not Applicable.

Steps to Reproduce



Run an Agent using PRutils command line option.

Resolution



Agents can be started using the PRUtils command line utility with 'runagent' argument and by specifying the Agent name and Agent ruleset.

Agents are running even at user's environment and following log statements confirm this:

2015-04-16 10:22:52,347 [ cjs0stl41] [ STANDARD] [ ] ( internal.mgmt.EngineImpl) INFO - Embedded Environment initialization is complete.
2015-04-16 10:22:52,354 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Rule Set = Pega-ProCom Agent Name=AgentBulkProcessing
2015-04-16 10:22:52,354 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Agents enabled. Finding Agent Queue (Data-Agent-Queue) for AgentBulkProcessing
2015-04-16 10:22:52,354 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Attemt :1. Finding Data-Agent-Queue instance...
2015-04-16 10:22:52,357 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Schedules not created yet for rule set Pega-ProCom
2015-04-16 10:23:22,363 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Attemt :2. Finding Data-Agent-Queue instance...
2015-04-16 10:23:22,365 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Schedules not created yet for rule set Pega-ProCom
2015-04-16 10:23:52,372 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Attemt :3. Finding Data-Agent-Queue instance...
2015-04-16 10:23:52,372 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Schedules not created yet for rule set Pega-ProCom
2015-04-16 10:23:59,169 [egaRULES-MasterAgent] [ STANDARD] [ ] ( internal.async.Agent) INFO - System date: Thu Apr 16 10:23:59 CDT 2015 Total memory: 385,062,912 Free memory: 88,399,472 Requestor Count: 8 Shared Pages memory usage: 0%
2015-04-16 10:24:00,845 [egaRULES-MasterAgent] [ STANDARD] [ ] (l.access.RuleCandidateIterator) INFO - Single candidate rule resolution optimization is enabled
2015-04-16 10:24:04,361 [egaRULES-MasterAgent] [ STANDARD] [ ] (y.translator.TranslatorHarness) INFO - Using translator/grammars v3new
2015-04-16 10:24:09,876 [egaRULES-MasterAgent] [ STANDARD] [ ] ( priv.factory.ByteArrayFactory) INFO - Factory-Internal pool expansion for ByteArray[1024] from 20 up to 40.
2015-04-16 10:24:09,876 [egaRULES-MasterAgent] [ STANDARD] [ ] ( priv.factory.ByteArrayFactory) INFO - Factory-Internal pool expansion for ByteArray[1024] from 40 up to 80.
2015-04-16 10:24:22,373 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Attemt :4. Finding Data-Agent-Queue instance...
2015-04-16 10:24:22,373 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Schedule of Agent AgentBulkProcessing found.
2015-04-16 10:24:22,373 [ cjs0stl41] [ STANDARD] [ ] (al.util.AgentManagementUtility) INFO - Found Data-Agent-Queue instance successfully


Following are the answers to the queries raised by the developer -
a) When you run the Agent from command line, it will run in a separate mode.
b) Pega does not have PRutils command-line option to select specific node or nodeID to run the Agent.
c) Pega cannot stop the Agent from command-line.

Published July 29, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us