<?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 java 1.4.2 garbage collector performance in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/java-1-4-2-garbage-collector-performance/m-p/3723244#M4017</link>
    <description>Hi, &lt;BR /&gt;we're using java version "1.4.2"&lt;BR /&gt;Java(TM) 2 Runtime Environment, Standard Edition&lt;BR /&gt;Fast VM (build 1.4.2-4.p2, native threads, mixed mode, 05/10/2005-02:43)&lt;BR /&gt;on OSF1  V5.1 2650 alpha, to run a weblogic 8.1 server.&lt;BR /&gt;&lt;BR /&gt;We're having a problem where the server times out when the garbage collection phase takes 30 seconds or more. I've raised this with BEA but they're tending to blame the jvm for this and aren't too clued up on this implementation.&lt;BR /&gt;&lt;BR /&gt;So the question is, should the garbage collection take this long, and should a client hang whilst it's going on?&lt;BR /&gt;&lt;BR /&gt;I've been doing some experiments, and if I have minimal apps running, no heap specified, the server runs happily with 100Mb  of heap and does the collecting c. 0.1 seconds.  If I increase the heap size to c. 500Mb, the garbage collection takes 10-30 seconds (I increase the heap either explicitly with -Xms java flag or grow it by grabbing memory in other apps - the net effect is the same).&lt;BR /&gt;&lt;BR /&gt;The machine has 1Gb of memory, we're trying to run 2 weblogic servers on it.  No java flags specified other than -Xverbosegc&lt;BR /&gt;&lt;BR /&gt;TIA,&lt;BR /&gt;John</description>
    <pubDate>Thu, 02 Feb 2006 11:43:54 GMT</pubDate>
    <dc:creator>John Turnbull</dc:creator>
    <dc:date>2006-02-02T11:43:54Z</dc:date>
    <item>
      <title>java 1.4.2 garbage collector performance</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/java-1-4-2-garbage-collector-performance/m-p/3723244#M4017</link>
      <description>Hi, &lt;BR /&gt;we're using java version "1.4.2"&lt;BR /&gt;Java(TM) 2 Runtime Environment, Standard Edition&lt;BR /&gt;Fast VM (build 1.4.2-4.p2, native threads, mixed mode, 05/10/2005-02:43)&lt;BR /&gt;on OSF1  V5.1 2650 alpha, to run a weblogic 8.1 server.&lt;BR /&gt;&lt;BR /&gt;We're having a problem where the server times out when the garbage collection phase takes 30 seconds or more. I've raised this with BEA but they're tending to blame the jvm for this and aren't too clued up on this implementation.&lt;BR /&gt;&lt;BR /&gt;So the question is, should the garbage collection take this long, and should a client hang whilst it's going on?&lt;BR /&gt;&lt;BR /&gt;I've been doing some experiments, and if I have minimal apps running, no heap specified, the server runs happily with 100Mb  of heap and does the collecting c. 0.1 seconds.  If I increase the heap size to c. 500Mb, the garbage collection takes 10-30 seconds (I increase the heap either explicitly with -Xms java flag or grow it by grabbing memory in other apps - the net effect is the same).&lt;BR /&gt;&lt;BR /&gt;The machine has 1Gb of memory, we're trying to run 2 weblogic servers on it.  No java flags specified other than -Xverbosegc&lt;BR /&gt;&lt;BR /&gt;TIA,&lt;BR /&gt;John</description>
      <pubDate>Thu, 02 Feb 2006 11:43:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/java-1-4-2-garbage-collector-performance/m-p/3723244#M4017</guid>
      <dc:creator>John Turnbull</dc:creator>
      <dc:date>2006-02-02T11:43:54Z</dc:date>
    </item>
  </channel>
</rss>

