<?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: memory leakage in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599082#M829374</link>
    <description>The combination of products you listed did not make much sense to me as most people run either apache or (pay for and run) iplanet or with its new name sun one server but anyways, here is a couple of commands that you can run to find offending programs:&lt;BR /&gt;&lt;BR /&gt;UNIX95= ps -eo vsz,pid,args,ruser | sort -rn &lt;BR /&gt;&lt;BR /&gt;or just to monitor httpd (for apache as an example)&lt;BR /&gt;&lt;BR /&gt;UNIX95= ps -C httpd -o vsz,pid,ruser,args&lt;BR /&gt;&lt;BR /&gt;above are from my notes that I took from some previous itrc posts regarding memory leak issue. &lt;BR /&gt;&lt;BR /&gt;also check ipcs command usage on the man page. You can find few command line switches like -m or -b to monitor the memory usage.&lt;BR /&gt;&lt;BR /&gt;running these commands from cron hourly or more frequently if you can afford, and logging the output to a file for a few days time, may show you if something is sticking out.&lt;BR /&gt;&lt;BR /&gt;memory leaks are caused by sloppy programmers whose code does not release the memory they grabbed after the exit. Find the offending process and talk to the application developer.&lt;BR /&gt;</description>
    <pubDate>Mon, 08 Aug 2005 23:58:26 GMT</pubDate>
    <dc:creator>Mel Burslan</dc:creator>
    <dc:date>2005-08-08T23:58:26Z</dc:date>
    <item>
      <title>memory leakage</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599081#M829373</link>
      <description>Sir, &lt;BR /&gt;&lt;BR /&gt;We are using hp apache, weblogic and iplanet web server on hpux 11i.&lt;BR /&gt;&lt;BR /&gt;I suspect some of them might be producing memory leakage.&lt;BR /&gt;&lt;BR /&gt;Can someone suggest how to find out memory leakage ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv</description>
      <pubDate>Mon, 08 Aug 2005 23:23:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599081#M829373</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2005-08-08T23:23:17Z</dc:date>
    </item>
    <item>
      <title>Re: memory leakage</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599082#M829374</link>
      <description>The combination of products you listed did not make much sense to me as most people run either apache or (pay for and run) iplanet or with its new name sun one server but anyways, here is a couple of commands that you can run to find offending programs:&lt;BR /&gt;&lt;BR /&gt;UNIX95= ps -eo vsz,pid,args,ruser | sort -rn &lt;BR /&gt;&lt;BR /&gt;or just to monitor httpd (for apache as an example)&lt;BR /&gt;&lt;BR /&gt;UNIX95= ps -C httpd -o vsz,pid,ruser,args&lt;BR /&gt;&lt;BR /&gt;above are from my notes that I took from some previous itrc posts regarding memory leak issue. &lt;BR /&gt;&lt;BR /&gt;also check ipcs command usage on the man page. You can find few command line switches like -m or -b to monitor the memory usage.&lt;BR /&gt;&lt;BR /&gt;running these commands from cron hourly or more frequently if you can afford, and logging the output to a file for a few days time, may show you if something is sticking out.&lt;BR /&gt;&lt;BR /&gt;memory leaks are caused by sloppy programmers whose code does not release the memory they grabbed after the exit. Find the offending process and talk to the application developer.&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Aug 2005 23:58:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599082#M829374</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2005-08-08T23:58:26Z</dc:date>
    </item>
    <item>
      <title>Re: memory leakage</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599083#M829375</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;All the tools you need at&lt;BR /&gt;&lt;BR /&gt;ftp://eh:spear9@hprc.external.hp.com/memory.htm&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;           Steve Steel</description>
      <pubDate>Tue, 09 Aug 2005 03:05:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599083#M829375</guid>
      <dc:creator>Steve Steel</dc:creator>
      <dc:date>2005-08-09T03:05:58Z</dc:date>
    </item>
    <item>
      <title>Re: memory leakage</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599084#M829376</link>
      <description>For detecting memory leak, you have to buy commertial tool like purify and insure++.&lt;BR /&gt;&lt;BR /&gt;gdb (wdb) in some versions are supporting possibility to detect memory leak. We can use info leaks command on gdb to detect this.&lt;BR /&gt;&lt;BR /&gt;A small document written to get memory leak in small c program is given here as,&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://geocities.com/kmuthu_gct/memoryleak_gdb.html" target="_blank"&gt;http://geocities.com/kmuthu_gct/memoryleak_gdb.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;hth.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Aug 2005 03:17:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599084#M829376</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2005-08-09T03:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: memory leakage</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599085#M829377</link>
      <description>I can't comment on iPlanat (aka SUN ONE) Webserver since we don't run this product.&lt;BR /&gt;That you run all the named webservers on a single machine would only make sense to me if that was a development workplace or similar.&lt;BR /&gt;We do however run a BEA Weblogic server (which I think is entirely Java J2EE).&lt;BR /&gt;Afaik, the Java VM is running its own garbage collector that should (theoretically) free unrefernced memory segments, and thus avoid memory leakages.&lt;BR /&gt;However, I've also heard from the developers who set up our Weblogic application that a knowledgeable Java hacker can circumvent the Java garbage collector and initate collection time slices at random.&lt;BR /&gt;I can't recall what the technique was called.&lt;BR /&gt;But this in mind also shows potential for memory leaks with Weblogic apps to me.&lt;BR /&gt; &lt;BR /&gt;Yet another story is Apache if your webdevelopers make use of modules like mod_perl.&lt;BR /&gt;An inconsiderate coder who isn't initializing and freeing resources (data structure, objects etc.) as recommended by the mod_perl guidelines, might very well produce memory leaks, or even worse, severely impair the operation of Apache.&lt;BR /&gt; &lt;BR /&gt;SUN being the inventors of Java I would guess that iPlanet is also a purely Java technology.&lt;BR /&gt;So I could imagine that the same is thinkable as what I have said regarding Weblogic.&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Aug 2005 03:46:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leakage/m-p/3599085#M829377</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2005-08-09T03:46:33Z</dc:date>
    </item>
  </channel>
</rss>

