I could not able to kill two process which is running in the required port for me.Can any body help me to kill the exiting process.
- 27000908 - - - <exiting>
- 30998528 - - - <exiting>
all i know is as follows if kill -9 pid doesn't work nothing else will work ( as far as i know ) rebooting is the only way I know to clear these exiting processes. .
exiting process must free all of the resources it has before
completely exited, otherwise all kinds of side effects can occur such as
memory leaks, filesystems where you can't free up space or unmount them, etc.
Thank you h@foorsa for your response.I am not able to kill these process with kill -9 also tried different options.This is coming now frequently (within two /three days) when I am going to restart my weblogic application.Any idea why it is happening?
Typical cause for unkillable process is pending IO like bad magnetic tape or NFS server went away.
Are you using solaris ?
I am using AIX and when running my weblogic application the system is getting hung.When i am trying to kill or stop the process and reboot again then it is showing that the port is used by another process.After finding the process id for the port ,I found the process id is in exiting state and not able to kill those process anyway.Only after rebooting the issue has been resolved.I need help on why the application is getting hung and also if there is any way to kill the process of exiting state
Did you check weblogic and AIX error logs?? maybe you get some info about the warning from there
wait for it to finish up or reboot.
those seem to be orphan process, it is better to wait for a reboot
I don't use AIX but in general an "exiting" process has begun to run the exit system call. Killing it won't help, it is already trying to exit. Of of the things that exit() does is to close all open files and my guess is that you are hanging on that. I don't know about AIX, but on Solaris and Linux and HP-UX, we can use a program called lsof to list the open files of a process. I would try to find out which files are still opened. Opened files on a non-responsive NFS server are indeed a very good bet. Once I was sitting at a system console and my knee hit the power button on a disk drive. This caused some exiting processes and a lot of other trouble as well. I powered the drive back on and it recovered.
This may or may not be an orphan. Orphans are quickly adopted by init and there is nothing wrong with being an orphan. Non-orphaned processes risk being zombies if the parent does not wait for them. But in any case, a process must complete the exit syetem call to finish dying. One of the last tasks of exit() is to notify the parent of the death of a child. If the the parent is swapped out, it may need to be swapped back in to receive the notification. If there is no room to swap it in, the kernel must wait until room is available and exit() could hang for this reason. But there would be more indications of trouble if this was the case.
If you're running system accounting, the exit call needs to write a record in the accounting file to record the process exit. I have often wondered what would happen if the file system was full and the record could not be written. But this seems to have the potential for trouble as well. And these are the only things I can think of that might cause the problem.