<?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>Kommentare zu: Java Memory Problems</title>
	<atom:link href="http://blog.dynatrace.com/2009/08/13/java-memory-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 12:12:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>Von: Top 10 Performance Problems &#171; Microtime Computers</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/comment-page-1/#comment-59536</link>
		<dc:creator>Top 10 Performance Problems &#171; Microtime Computers</dc:creator>
		<pubDate>Wed, 14 Sep 2011 14:57:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724#comment-59536</guid>
		<description>[...] Reads: Java Memory Problems, Identify GC Bottlenecks in Distributed [...]</description>
		<content:encoded><![CDATA[<p>[...] Reads: Java Memory Problems, Identify GC Bottlenecks in Distributed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Emma Roberts</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/comment-page-1/#comment-59398</link>
		<dc:creator>Emma Roberts</dc:creator>
		<pubDate>Tue, 06 Sep 2011 12:14:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724#comment-59398</guid>
		<description>handle removing the old reference to the array before initializing the new one. Fortunately the array was the same size, so it could be reused.</description>
		<content:encoded><![CDATA[<p>handle removing the old reference to the array before initializing the new one. Fortunately the array was the same size, so it could be reused.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: dating after 40</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/comment-page-1/#comment-45370</link>
		<dc:creator>dating after 40</dc:creator>
		<pubDate>Mon, 09 May 2011 14:23:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724#comment-45370</guid>
		<description>What an excellent blog! If they go up any time you redeploy your application, then a classloader leak is a likely reason for the problem.</description>
		<content:encoded><![CDATA[<p>What an excellent blog! If they go up any time you redeploy your application, then a classloader leak is a likely reason for the problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: free online sex date</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/comment-page-1/#comment-45368</link>
		<dc:creator>free online sex date</dc:creator>
		<pubDate>Mon, 09 May 2011 14:14:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724#comment-45368</guid>
		<description>Thanks for the information! I once had a oom exception when replacing a large array. The GC (JVM spec?) couldn’t handle removing the old reference to the array before initializing the new one. Fortunately the array was the same size, so it could be reused.</description>
		<content:encoded><![CDATA[<p>Thanks for the information! I once had a oom exception when replacing a large array. The GC (JVM spec?) couldn’t handle removing the old reference to the array before initializing the new one. Fortunately the array was the same size, so it could be reused.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Quora</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/comment-page-1/#comment-20924</link>
		<dc:creator>Quora</dc:creator>
		<pubDate>Fri, 01 Oct 2010 13:39:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724#comment-20924</guid>
		<description>&lt;strong&gt;What are some useful tips for tuning programs running on the JVM?...&lt;/strong&gt;

Some more: * GC Tuning in the HotSpot Java VM - a FISL 10 Presentation:  http://www.slideshare.net/ludomp/gc-tuning-in-the-hotspot-java-vm-a-fisl-10-presentation  * A list of JVM options for JVM 6: http://www.md.pp.ru/~eu/jdk6options.html * Java Memory...</description>
		<content:encoded><![CDATA[<p><strong>What are some useful tips for tuning programs running on the JVM?&#8230;</strong></p>
<p>Some more: * GC Tuning in the HotSpot Java VM &#8211; a FISL 10 Presentation:  http://www.slideshare.net/ludomp/gc-tuning-in-the-hotspot-java-vm-a-fisl-10-presentation  * A list of JVM options for JVM 6: <a href="http://www.md.pp.ru/~eu/jdk6options.html" rel="nofollow"></a><a href='http://www.md.pp.ru/~eu/jdk6options.html'>http://www.md.pp.ru/~eu/jdk6options.html</a> * Java Memory&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Markus Kohler</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/comment-page-1/#comment-20702</link>
		<dc:creator>Markus Kohler</dc:creator>
		<pubDate>Mon, 27 Sep 2010 09:09:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724#comment-20702</guid>
		<description>http://eclipse.org/mat/ can easily (on a 64 bit OS) analyze heap dumps &gt;6Gbyte. I&#039;ve done that since years. 
I agree with your statement that just increasing the heap size is not the solution. At some point you will still &quot;hit the wall&quot;: 

And then in a clustered environment you would have to transfer the session to another node. The larger the session the longer it will take. 
Greetings,
Markus</description>
		<content:encoded><![CDATA[<p><a href="http://eclipse.org/mat/" rel="nofollow"></a><a href='http://eclipse.org/mat/'>http://eclipse.org/mat/</a> can easily (on a 64 bit OS) analyze heap dumps &gt;6Gbyte. I&#8217;ve done that since years.<br />
I agree with your statement that just increasing the heap size is not the solution. At some point you will still &#8220;hit the wall&#8221;: </p>
<p>And then in a clustered environment you would have to transfer the session to another node. The larger the session the longer it will take.<br />
Greetings,<br />
Markus</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: zercath</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/comment-page-1/#comment-17243</link>
		<dc:creator>zercath</dc:creator>
		<pubDate>Wed, 14 Jul 2010 17:39:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724#comment-17243</guid>
		<description>Could someone get a better deal with a 645 and Phase One back… Totally.  But if you are a pro studio guy and what clean files, the S2 delivers although not a real medium format.  Gee we see her contact lenses.  As for the Leicas not being used…well it is a shame but for those who do it is very rewarding.  I bought my M8.2 because I was fed up of coming back with 3000 pics of the same things, Leica slows me down and helps me artistically.</description>
		<content:encoded><![CDATA[<p>Could someone get a better deal with a 645 and Phase One back… Totally.  But if you are a pro studio guy and what clean files, the S2 delivers although not a real medium format.  Gee we see her contact lenses.  As for the Leicas not being used…well it is a shame but for those who do it is very rewarding.  I bought my M8.2 because I was fed up of coming back with 3000 pics of the same things, Leica slows me down and helps me artistically.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Top 10 Performance Problems taken from Zappos, Monster, Thomson and Co &#124; Blue74</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/comment-page-1/#comment-17204</link>
		<dc:creator>Top 10 Performance Problems taken from Zappos, Monster, Thomson and Co &#124; Blue74</dc:creator>
		<pubDate>Tue, 13 Jul 2010 15:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724#comment-17204</guid>
		<description>[...] Reads: Java Memory Problems, Identify GC Bottlenecks in Distributed [...]</description>
		<content:encoded><![CDATA[<p>[...] Reads: Java Memory Problems, Identify GC Bottlenecks in Distributed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Andy Fields</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/comment-page-1/#comment-17081</link>
		<dc:creator>Andy Fields</dc:creator>
		<pubDate>Fri, 09 Jul 2010 19:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724#comment-17081</guid>
		<description>Great article thanks! I&#039;ve been using a product from OPNET called Panorama to find these production application issues, but I like your GUI!</description>
		<content:encoded><![CDATA[<p>Great article thanks! I&#8217;ve been using a product from OPNET called Panorama to find these production application issues, but I like your GUI!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Top 10 Performance Problems taken from Zappos, Monster, Thomson and Co Performance, Scalability and Architecture &#8211; Java and .NET Application Performance Management (dynaTrace Blog)</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/comment-page-1/#comment-16506</link>
		<dc:creator>Top 10 Performance Problems taken from Zappos, Monster, Thomson and Co Performance, Scalability and Architecture &#8211; Java and .NET Application Performance Management (dynaTrace Blog)</dc:creator>
		<pubDate>Wed, 16 Jun 2010 18:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724#comment-16506</guid>
		<description>[...] Reads: Java Memory Problems, Identify GC Bottlenecks in Distributed [...]</description>
		<content:encoded><![CDATA[<p>[...] Reads: Java Memory Problems, Identify GC Bottlenecks in Distributed [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

