<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Java Memory Leaks</title>
	<atom:link href="http://www.performanceengineer.com/blog/java-memory-leaks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.performanceengineer.com/blog/java-memory-leaks/</link>
	<description>Software Performance Engineering &#38; Testing</description>
	<lastBuildDate>Wed, 02 Dec 2009 14:39:21 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: loolek</title>
		<link>http://www.performanceengineer.com/blog/java-memory-leaks/comment-page-1/#comment-328</link>
		<dc:creator>loolek</dc:creator>
		<pubDate>Tue, 24 Feb 2009 13:07:09 +0000</pubDate>
		<guid isPermaLink="false">#comment-328</guid>
		<description>This is a good tool too -&gt;

http://www.alphaworks.ibm.com/tech/heapanalyzer

-- 
&quot;No trees were destroyed in the sending of this message.
However, a large number of electrons were terribly inconvenienced.&quot;</description>
		<content:encoded><![CDATA[<p>This is a good tool too -&gt;</p>
<p><a href="http://www.alphaworks.ibm.com/tech/heapanalyzer" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.alphaworks.ibm.com/tech/heapanalyzer?referer=');">http://www.alphaworks.ibm.com/tech/heapanalyzer</a></p>
<p>&#8211;<br />
&#8220;No trees were destroyed in the sending of this message.<br />
However, a large number of electrons were terribly inconvenienced.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nirmal</title>
		<link>http://www.performanceengineer.com/blog/java-memory-leaks/comment-page-1/#comment-301</link>
		<dc:creator>Nirmal</dc:creator>
		<pubDate>Tue, 14 Oct 2008 12:32:12 +0000</pubDate>
		<guid isPermaLink="false">#comment-301</guid>
		<description>Hi,

I am using jmap on Linux (JVM is 1.5.0_15-b04).

I use the following command to take the heap dump:
     jmap -heap:format=b 

This creates a heap dump file in my current directory as &quot;heap.bin&quot;.

I then copied this heap.bin from Linux to windows using Winscp.

But from windows when I open this file in SAP Memory Analyzer(with open snapshot) it gives me the following error:
org.eclipse.core.runtime.CoreException: Text editor does not have a document provider
	at org.eclipse.ui.texteditor.AbstractTextEditor.doSetInput(AbstractTextEditor.java:3928)
	at org.eclipse.ui.texteditor.StatusTextEditor.doSetInput(StatusTextEditor.java:190)
	at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.doSetInput(AbstractDecoratedTextEditor.java:1225)
	at org.eclipse.ui.editors.text.TextEditor.doSetInput(TextEditor.java:168)
	at org.eclipse.ui.texteditor.AbstractTextEditor$19.run(AbstractTextEditor.java:2994)
	at 

I even renamed the dump file to &quot;heap.hprof&quot; as in the sample snapshots of SAP memory Analyzer the filenames are: &quot;HeapDumpSample.hprof&quot;

Please help me in opening the heap dump file from jmap in SAP Memory Analyzer.

Where did I make a mistake?

Nirmal.....</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I am using jmap on Linux (JVM is 1.5.0_15-b04).</p>
<p>I use the following command to take the heap dump:<br />
     jmap -heap:format=b </p>
<p>This creates a heap dump file in my current directory as &#8220;heap.bin&#8221;.</p>
<p>I then copied this heap.bin from Linux to windows using Winscp.</p>
<p>But from windows when I open this file in SAP Memory Analyzer(with open snapshot) it gives me the following error:<br />
org.eclipse.core.runtime.CoreException: Text editor does not have a document provider<br />
	at org.eclipse.ui.texteditor.AbstractTextEditor.doSetInput(AbstractTextEditor.java:3928)<br />
	at org.eclipse.ui.texteditor.StatusTextEditor.doSetInput(StatusTextEditor.java:190)<br />
	at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.doSetInput(AbstractDecoratedTextEditor.java:1225)<br />
	at org.eclipse.ui.editors.text.TextEditor.doSetInput(TextEditor.java:168)<br />
	at org.eclipse.ui.texteditor.AbstractTextEditor$19.run(AbstractTextEditor.java:2994)<br />
	at </p>
<p>I even renamed the dump file to &#8220;heap.hprof&#8221; as in the sample snapshots of SAP memory Analyzer the filenames are: &#8220;HeapDumpSample.hprof&#8221;</p>
<p>Please help me in opening the heap dump file from jmap in SAP Memory Analyzer.</p>
<p>Where did I make a mistake?</p>
<p>Nirmal&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: charlie</title>
		<link>http://www.performanceengineer.com/blog/java-memory-leaks/comment-page-1/#comment-300</link>
		<dc:creator>charlie</dc:creator>
		<pubDate>Mon, 13 Oct 2008 18:36:53 +0000</pubDate>
		<guid isPermaLink="false">#comment-300</guid>
		<description>I suspect it is either you don&#039;t have permission to write to the current directory, or you aren&#039;t running jmap as the owner of the process.</description>
		<content:encoded><![CDATA[<p>I suspect it is either you don&#8217;t have permission to write to the current directory, or you aren&#8217;t running jmap as the owner of the process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John P. Anderson</title>
		<link>http://www.performanceengineer.com/blog/java-memory-leaks/comment-page-1/#comment-299</link>
		<dc:creator>John P. Anderson</dc:creator>
		<pubDate>Mon, 13 Oct 2008 12:25:01 +0000</pubDate>
		<guid isPermaLink="false">#comment-299</guid>
		<description>I tried running your command (jmap -heap:format=b $pid) but all I get is the following:

Attaching to process ID 6535, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 1.5.0_15-b04
heap.bin (Permission denied)

Anyone got any idea of what is happening here?</description>
		<content:encoded><![CDATA[<p>I tried running your command (jmap -heap:format=b $pid) but all I get is the following:</p>
<p>Attaching to process ID 6535, please wait&#8230;<br />
Debugger attached successfully.<br />
Server compiler detected.<br />
JVM version is 1.5.0_15-b04<br />
heap.bin (Permission denied)</p>
<p>Anyone got any idea of what is happening here?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: charlie</title>
		<link>http://www.performanceengineer.com/blog/java-memory-leaks/comment-page-1/#comment-200</link>
		<dc:creator>charlie</dc:creator>
		<pubDate>Tue, 17 Jun 2008 14:39:19 +0000</pubDate>
		<guid isPermaLink="false">#comment-200</guid>
		<description>UPDATE:

The SAP Memory Analyzer is now an &lt;a href=&quot;http://www.eclipse.org/mat/&quot; rel=&quot;nofollow&quot;&gt;Eclipse project&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>UPDATE:</p>
<p>The SAP Memory Analyzer is now an <a href="http://www.eclipse.org/mat/" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.eclipse.org/mat/?referer=');">Eclipse project</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joychester</title>
		<link>http://www.performanceengineer.com/blog/java-memory-leaks/comment-page-1/#comment-77</link>
		<dc:creator>joychester</dc:creator>
		<pubDate>Sun, 18 May 2008 13:01:39 +0000</pubDate>
		<guid isPermaLink="false">#comment-77</guid>
		<description>Charlie, 
You can try this way to use Jconsole 6 remotely to detect your application memory leak, even your application is under JDK5, not JDK6. (That means your remote dasktop or laptop is under JDK6)I am using this way very well :) 
(BTW,Jconsole in JDK5 is not good at all.)

For further analysis(personally speaking, I perfered to use Netbean heap walker) we should use other tools to support. if application is using JDK6, everything is good, you can extract memory heap snapshot banary file using &quot;Mbean&quot; tab. if application is under JDK5, then you need other tools to support.
Here we just talk about the open source solution.

---Joychester, Performance engineer</description>
		<content:encoded><![CDATA[<p>Charlie,<br />
You can try this way to use Jconsole 6 remotely to detect your application memory leak, even your application is under JDK5, not JDK6. (That means your remote dasktop or laptop is under JDK6)I am using this way very well <img src='http://www.performanceengineer.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
(BTW,Jconsole in JDK5 is not good at all.)</p>
<p>For further analysis(personally speaking, I perfered to use Netbean heap walker) we should use other tools to support. if application is using JDK6, everything is good, you can extract memory heap snapshot banary file using &#8220;Mbean&#8221; tab. if application is under JDK5, then you need other tools to support.<br />
Here we just talk about the open source solution.</p>
<p>&#8212;Joychester, Performance engineer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://www.performanceengineer.com/blog/java-memory-leaks/comment-page-1/#comment-76</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Tue, 13 May 2008 14:34:47 +0000</pubDate>
		<guid isPermaLink="false">#comment-76</guid>
		<description>As you point out, jconsole can be good for detection, but once you&#039;ve identified a memory leak exists, you have to move to other tools to find root cause.

In general, the java tools are much improved in Java 6, but a lot of people aren&#039;t on Java 6 in production systems.  So I&#039;m stuck with Java 5 and the problems that jmap has in some older revisions (at least updates 11 and 12 are known to have the issue described above).  

</description>
		<content:encoded><![CDATA[<p>As you point out, jconsole can be good for detection, but once you&#8217;ve identified a memory leak exists, you have to move to other tools to find root cause.</p>
<p>In general, the java tools are much improved in Java 6, but a lot of people aren&#8217;t on Java 6 in production systems.  So I&#8217;m stuck with Java 5 and the problems that jmap has in some older revisions (at least updates 11 and 12 are known to have the issue described above).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joychester</title>
		<link>http://www.performanceengineer.com/blog/java-memory-leaks/comment-page-1/#comment-74</link>
		<dc:creator>joychester</dc:creator>
		<pubDate>Mon, 12 May 2008 16:22:30 +0000</pubDate>
		<guid isPermaLink="false">#comment-74</guid>
		<description>here is my practice based on my daily testing work, not that hard if you make it systemiclly:
1.jconsole is a very good tool for detecting java memory leak issue at first. 
2.narrow down the test cases or senarios to find which part may cause the problem
3.also i love jmap to get heap dump snapshot to get deep analysis after we are clear we have an issue on memory.
4. use some tool to read the binary heap dump file if necessary
--Joychester,performance testing engineer</description>
		<content:encoded><![CDATA[<p>here is my practice based on my daily testing work, not that hard if you make it systemiclly:<br />
1.jconsole is a very good tool for detecting java memory leak issue at first.<br />
2.narrow down the test cases or senarios to find which part may cause the problem<br />
3.also i love jmap to get heap dump snapshot to get deep analysis after we are clear we have an issue on memory.<br />
4. use some tool to read the binary heap dump file if necessary<br />
&#8211;Joychester,performance testing engineer</p>
]]></content:encoded>
	</item>
</channel>
</rss>
