<?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: ISEE Java hogging CPU in Insight Remote Support</title>
    <link>https://community.hpe.com/t5/insight-remote-support/isee-java-hogging-cpu/m-p/5020089#M3598</link>
    <description>Mike,&lt;BR /&gt;&lt;BR /&gt;java -DRu belongs to Runner application.&lt;BR /&gt;&lt;BR /&gt;You can stop/start Runner by:&lt;BR /&gt;/sbin/init.d/runner stop/start&lt;BR /&gt;&lt;BR /&gt;You can disable Runner from startup during bootime:&lt;BR /&gt;/etc/rc.config.d/runner.conf&lt;BR /&gt;START_RUNNER = 0&lt;BR /&gt;&lt;BR /&gt;Runner is an application mostly used by HP Account Team for Mission Critical Server. Runner records up/down time.&lt;BR /&gt;&lt;BR /&gt;If this Server is a Mission Critical Server, you may want to notify your ASE of the problem, if it's not a MC Server, I think you should disable Runner.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 22 Dec 2006 15:53:06 GMT</pubDate>
    <dc:creator>Liem Nguyen</dc:creator>
    <dc:date>2006-12-22T15:53:06Z</dc:date>
    <item>
      <title>ISEE Java hogging CPU</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-java-hogging-cpu/m-p/5020088#M3597</link>
      <description>We had an issue where the Java process for ISEE was using up the CPU on our server:&lt;BR /&gt;&lt;BR /&gt;/opt/hpservices/jre/opt/java1.4/jre/bin/PA_RISC2.0/java -DRunne&lt;BR /&gt;&lt;BR /&gt;The top command showed:&lt;BR /&gt;CPU TTY    PID USERNAME PRI NI   SIZE    RES STATE    TIME %WCPU  %CPU COMMAND&lt;BR /&gt;&lt;BR /&gt; 6   ?    8455 root     152 20   249M 65956K run    799:00 200.30 199.95 java&lt;BR /&gt;&lt;BR /&gt; 1   ?   28481 oracle   154 20  5294M  7412K sleep    7:20  4.54  4.53 oraclevpsebl&lt;BR /&gt;&lt;BR /&gt;Any idea why this would occur ??&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 21 Dec 2006 15:45:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-java-hogging-cpu/m-p/5020088#M3597</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2006-12-21T15:45:24Z</dc:date>
    </item>
    <item>
      <title>Re: ISEE Java hogging CPU</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-java-hogging-cpu/m-p/5020089#M3598</link>
      <description>Mike,&lt;BR /&gt;&lt;BR /&gt;java -DRu belongs to Runner application.&lt;BR /&gt;&lt;BR /&gt;You can stop/start Runner by:&lt;BR /&gt;/sbin/init.d/runner stop/start&lt;BR /&gt;&lt;BR /&gt;You can disable Runner from startup during bootime:&lt;BR /&gt;/etc/rc.config.d/runner.conf&lt;BR /&gt;START_RUNNER = 0&lt;BR /&gt;&lt;BR /&gt;Runner is an application mostly used by HP Account Team for Mission Critical Server. Runner records up/down time.&lt;BR /&gt;&lt;BR /&gt;If this Server is a Mission Critical Server, you may want to notify your ASE of the problem, if it's not a MC Server, I think you should disable Runner.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Dec 2006 15:53:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-java-hogging-cpu/m-p/5020089#M3598</guid>
      <dc:creator>Liem Nguyen</dc:creator>
      <dc:date>2006-12-22T15:53:06Z</dc:date>
    </item>
    <item>
      <title>Re: ISEE Java hogging CPU</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-java-hogging-cpu/m-p/5020090#M3599</link>
      <description>Liem&lt;BR /&gt;&lt;BR /&gt;Thanks alot for your response. This is running on a MC server so I will pass this information on to our ASE.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Fri, 22 Dec 2006 17:12:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-java-hogging-cpu/m-p/5020090#M3599</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2006-12-22T17:12:12Z</dc:date>
    </item>
  </channel>
</rss>

