From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1M0tp9-0005uN-Ex for garchives@archives.gentoo.org; Mon, 04 May 2009 08:46:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8374FE03C2; Mon, 4 May 2009 08:46:24 +0000 (UTC) Received: from viefep16-int.chello.at (viefep16-int.chello.at [62.179.121.36]) by pigeon.gentoo.org (Postfix) with ESMTP id 0431BE03C2 for ; Mon, 4 May 2009 08:46:23 +0000 (UTC) Received: from edge02.upc.biz ([192.168.13.237]) by viefep16-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090504084622.GLDM3549.viefep16-int.chello.at@edge02.upc.biz>; Mon, 4 May 2009 10:46:22 +0200 Received: from [192.168.1.100] ([62.24.83.9]) by edge02.upc.biz with edge id nLmL1b04Y0C4Fjy02LmMn9; Mon, 04 May 2009 10:46:22 +0200 X-SourceIP: 62.24.83.9 Message-ID: <49FEAB5C.2040104@gentoo.org> Date: Mon, 04 May 2009 10:46:20 +0200 From: Vlastimil Babka User-Agent: Thunderbird 2.0.0.21 (X11/20090430) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-java@lists.gentoo.org MIME-Version: 1.0 To: Adam Carter CC: "gentoo-java@lists.gentoo.org" Subject: Re: [gentoo-java] Memory heap size problem References: <5602B0BD6D59AE4791BE83104940118DC11A58D8@excprdmbxw002.optus.com.au> In-Reply-To: <5602B0BD6D59AE4791BE83104940118DC11A58D8@excprdmbxw002.optus.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: a06fed27-acef-415b-8760-0be7451f86de X-Archives-Hash: 5fbcf683c10a8a65d838858a2c43e14b Adam Carter wrote: > A cisco web java gui is complaing "Your current java memory heap size > is less than 256 MB. You must increate the Java memory heap size" > etc. On windows and on a previous gentoo x86 box putting -Xmx256m in > the java applet runtime settings makes it work. This box is a newly > build amd64. Hi, I don't know this app, but I'd just try 512m instead of 256m... amd64 tends to need more than x86 :) I'm not sure the app can test the parameter directly, they probably run out of heap and suggest this size which was known working on x86. Vlastimil > Looks like the .jnlp is setting the memory; > > sphinx deployment # grep max /tmp/idm-1.jnlp initial-heap-size="64m" max-heap-size="256m"/> > > And the app is running with the required Xmx256m parameter; > > sphinx deployment # pgrep -lf java 10147 > /opt/sun-jdk-1.6.0.13/jre/bin/java -Xmx256m > -Xbootclasspath/a:/opt/sun-jdk-1.6.0.13/jre/lib/javaws.jar:/opt/sun-jdk-1.6.0.13/jre/lib/deploy.jar:/opt/sun-jdk-1.6.0.13/jre/lib/plugin.jar > -classpath /opt/sun-jdk-1.6.0.13/jre/lib/deploy.jar > -Djnlpx.vmargs=-Xmx256m > -Djnlpx.jvm=/opt/sun-jdk-1.6.0.13/jre/bin/java > -Djnlpx.splashport=36054 -Djnlpx.home=/opt/sun-jdk-1.6.0.13/jre/bin > -Djnlpx.remove=false -Djnlpx.offline=false -Djnlpx.relaunch=true > -Djnlpx.heapsize=67108864,268435456 > -Djava.security.policy=file:/opt/sun-jdk-1.6.0.13/jre/lib/security/javaws.policy > -DtrustProxy=true -Xverify:remote com.sun.javaws.Main > file:///tmp/idm-9.jnlp > > So it looks like it should work - any ideas on how to fix this? > (sun-jdk-1.6.0.13, also tried a 1.5 but had the same problem). > >