ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
R12.52SP1CR08 DE204473
Article ID: 127970
Updated On:
Products
CA Single Sign On Secure Proxy Server (SiteMinder)
CA Single Sign On SOA Security Manager (SiteMinder)
CA Single Sign-On
Issue/Introduction
Detail explanation is needed for the fix in R12.52 SP1 CR08.
00480586 DE204473 The LLAWP process fails to run when we kill it on an Apache web agent on Linux.
00480586 DE204473 The LLAWP process fails to run when we kill it on an Apache web agent on Linux.
Environment
Release: R12.52 SP1
Component: SMAPC
Component: SMAPC
Resolution
Symptom:
On Linux platform once we kill LLAWP process for Apache, it is not coming up in 12.52 SP1 CR5.
Fix Summary:
LLAWP Process ID is added to cache.
When the old LLAWP process is killed with kill -9 option, the LLAWP PID in cache remains as the PID of killed process. Hence the newly spawned LLAWP process detects that a LLAWP process is already exists and hence returns without filling the cache.
The modified code verifies whether any process is running with PID as given in cache. Only if the process is running, it returns true, else it replaces the value with the PID of new process and returns false.
On Linux platform once we kill LLAWP process for Apache, it is not coming up in 12.52 SP1 CR5.
Fix Summary:
LLAWP Process ID is added to cache.
When the old LLAWP process is killed with kill -9 option, the LLAWP PID in cache remains as the PID of killed process. Hence the newly spawned LLAWP process detects that a LLAWP process is already exists and hence returns without filling the cache.
The modified code verifies whether any process is running with PID as given in cache. Only if the process is running, it returns true, else it replaces the value with the PID of new process and returns false.
Feedback
Yes
No
Powered by
