<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: some java process can't be kill -9 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/some-java-process-can-t-be-kill-9/m-p/3102679#M147189</link>
    <description>Good comprehensive answer Matti.&lt;BR /&gt;&lt;BR /&gt;- ramd.</description>
    <pubDate>Mon, 27 Oct 2003 07:08:40 GMT</pubDate>
    <dc:creator>Ramkumar Devanathan</dc:creator>
    <dc:date>2003-10-27T07:08:40Z</dc:date>
    <item>
      <title>some java process can't be kill -9</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/some-java-process-can-t-be-kill-9/m-p/3102677#M147187</link>
      <description>&lt;BR /&gt;I have some stubborn java process that can be kill even with 'kill -9' run by root. How do I check what i/o, memory space or connection that it is tied to? I have lsof installed in this system.&lt;BR /&gt;&lt;BR /&gt;Other than rebooting the server, is there a way to find out what causes it to ignore -9 signal and refuse to stop.</description>
      <pubDate>Mon, 27 Oct 2003 03:49:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/some-java-process-can-t-be-kill-9/m-p/3102677#M147187</guid>
      <dc:creator>YLTan</dc:creator>
      <dc:date>2003-10-27T03:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: some java process can't be kill -9</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/some-java-process-can-t-be-kill-9/m-p/3102678#M147188</link>
      <description>A process that ignores kill -9 is often executing a system call. For some reason, the system call does not ever get finished.&lt;BR /&gt;&lt;BR /&gt;First, find the PID of the stubborn process.&lt;BR /&gt;&lt;BR /&gt;Check that the process is not already dead. If it is marked &lt;DEFUNCT&gt; in the "ps -fp &lt;PID&gt;" listing, the process is already dead but its parent process is not willing to receive notification of the process's death. If you stop the parent process, the dead child process should also get cleaned up.&lt;BR /&gt;&lt;BR /&gt;If you have NFS mounted disks, the processes that are using those disks will typically be stuck if the network connection to the NFS server fails.&lt;BR /&gt;&lt;BR /&gt;If you have GlancePlus installed, it has a "Process Wait States" display (key W) which might help. The "Process System Calls" display might also be useful.&lt;BR /&gt;&lt;BR /&gt;If you don't have Glance, do a "lsof -p &lt;PID&gt;" to see all the files the process is accessing. Are any of these on a NFS mounted disk?&lt;BR /&gt;&lt;BR /&gt;Do a "dmesg | tail -20" and see if you have SCSI resets or other error messages there. /var/adm/syslog/syslog.log may also have some messages. Those might mean that some hardware is either rudely disconnected or broken.&lt;BR /&gt;&lt;/PID&gt;&lt;/PID&gt;&lt;/DEFUNCT&gt;</description>
      <pubDate>Mon, 27 Oct 2003 07:03:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/some-java-process-can-t-be-kill-9/m-p/3102678#M147188</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2003-10-27T07:03:00Z</dc:date>
    </item>
    <item>
      <title>Re: some java process can't be kill -9</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/some-java-process-can-t-be-kill-9/m-p/3102679#M147189</link>
      <description>Good comprehensive answer Matti.&lt;BR /&gt;&lt;BR /&gt;- ramd.</description>
      <pubDate>Mon, 27 Oct 2003 07:08:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/some-java-process-can-t-be-kill-9/m-p/3102679#M147189</guid>
      <dc:creator>Ramkumar Devanathan</dc:creator>
      <dc:date>2003-10-27T07:08:40Z</dc:date>
    </item>
  </channel>
</rss>

