Stand-alone CLI Utility performance issues
Article ID: 6781
Updated On:
Products
Issue/Introduction
Customers who utilize the command line CLI program to trigger multiple events (upwards of 30 or more at one time) into the system may experience latency in processing of these requests. In some cases, a triggered event may even be missed/skipped.
Cause
This is a Java related issue where the random number generator /dev/random is being used instead of /dev/urandom.
Environment
Resolution
Some customers may choose to install the CLI utilities on an separate standalone server so as to minimize overhead on the DE Manager server. So, the change outlined below needs to be done on the machine where said CLI processing is being performed.
- Logon to the DE manager or the standalone server where you have the CLI utilities installed
- Navigate to <CAWA_HOME>/jre/lib/security/
- Open the java.security file using the editor of your choice.
- Comment out the line securerandom.source=file:/dev/random
- On the next line, add the line securerandom.source=file:/dev/./urandom
- Save the file
Note: This change does not require a restart of the DE services!
Additional Information
In the above examples, you need the crazy-looking filename, e.g., the extra /./, to trick Java into accepting your filename. If you just use /dev/urandom, Java decides you didn't really mean it and replaces what you wrote with /dev/random.
This behavior is addressed/fixed in the CA Workload Automation DE r12 SP1 release.
Feedback
