AIX

Dear ALL,

I'm working on a Siebel CRM enterprise which is completely on AIX 5.3 platform. I'm trying to find some information, in case you may be able to help.


Is there any command/procedure on AIX 5.3 by which I could check the blocked PIDs or lost PIDs for my Siebel Object Manager component. These process somehow are getting used by the Siebel Components (SCBroker) but they actually don't exist. This PID was actually started couple of days back and after that servers were brought down and PID got lost. But I could see the reference of same PID getting used for which no component exist on siebel side. There seems to be some blokage at OS level?

I am looking for some command which could get me the historic information of the lost PID. e.g what all threads were running on it when it was created couple of days back, what was actually going on during that time (some sort of historic tracing??)??

Input from AIX gurus would really help.

there is no historic process data on aix unless you have some kind of system monitoring (nagios/tivoli/bigbrother,zabbix,scom...)

I do not quite understand what you are trying to describe - to me it sounds like the parent process id is gone but the child processes are still there - just now owned by PID1 (the system)? In this case the processes are zombies and the only way to get rid of them is to reboot the system as they are useless hanging around eating system resources and you cannot kill them or remove them anyways.

Regards
zxmaus

Thanks for your reply!

Another issue I could see on AIX 5.3: At one of my customer they have got the ThreadLimit of 2500 set on web server in httpd.conf file.

Currently 2000 users have logged in each attaing a single instance of httpd.

While in ps -ef for httpd process it is showing thread count (thcount) almost 3000. This should have shown atmost 2500.

Why the difference?

presumably idle connections - so users that were connected and where the connection has not been cleanly disconnected after they finished using it. Your application should disconnect them after x minutes of idle time as each connection - even with idle - is eating memory

regards
zxmaus

Yes, these goes up and down. But, the point of concern is on top od ThreadLimit of 2500 there are so many connections. Almost 700-800 connections. WHich I think should not all be just idle connections, but few hanged up connections. Is there any formula how many additional idle connections would a 64-bit system running a 32-bit application could maintain? I don't think all would be idle, though there would be some. I don't have an exact idea how many???