Please note tuning exercises are of Support scope - in case any assistance is needed, please get in touch with your CA Account Manager to get local CA Services team involved.
Issues had been seen when Serverpath set were too similar (only differing in 1 character), therefore identical IPCS keys had been generated. Please double check and do a test changing one of the webagent's ServerPath to e.g. log directory.
Most common cause for such LLAWP shutdown error is that it does not shut down because there are other child processes still running. Due to webserver restart instead of start and stop with providing enough time for LLAWP to shutdown, too, there might be even duplicate LLAWP processes.
Please also check any startup and shut down scripts to make sure there is no kill command used for the web server which would leave LLAWP running, too.
Double check if necessary Solaris 10 patches are installed:
- BM HTTP Server patch IBM PQ 71734 for IBM HTTP Server 184.108.40.206 and 220.127.116.11
- 119963-08 (need this patch to avoid a runtime issue with Web Agent installation binaries)
You can check on patch versions by logging in as root and executing the following command: 'showrev -p | grep patchid'
If the LLAWP process does not shut down properly when shutting down the web server, shut down the LLAWP from the command line. This shuts down the running worker process associated with a WebAgent.conf file.
To shut down the LLAWP, use the command with this syntax: LLAWP path_to_WebAgent.conf -web_server_type -shutdown
For example: LLAWP /usr/apache/conf/WebAgent.conf -APACHE20 -shutdown
Note: Configuration file names and version strings that contain spaces should be surrounded by quotes, such as "value with spaces." The LLAWP process will take a few seconds to shut down.
Use the command line to shut the LLAWP down instead of the kill -9 command, so that the process cleans up shared system resources used by the Web Agent.
Double-check permissions for the user account used to launch the webserver to ensure you not run into any problem with permissions on webagent related files by reading and writing.
Upgrade webagent to a more current release to benefit from latest enhancement and fixes.
If issue is reproducible after taking all actions, please collect full webagent and webserver logs and traces, Core files and a pstack from the same time frame as the issue occurred when contacting CA Support.
This has been incorporated into the documentation. Please visit docops.ca.com for your version for updated information