Ok...

Configured a win2003 server with jdk5se with the -XX:+AggressiveHeap
-XX:+UseLargePages and the problem was that the system keeps with the same
error. More, it addresses only 1.1Gb ram TOTAL when in WXP it would address
a bit more.

So the good news is that it manages to "run" the JVM with more memory... but
doesn't use it and gives "out of heap memory" nevertheless.

Only now it takes a huge time before it crashs...

(will try when i've time with the JDK5EE version...
Cheers,
LF



Luis Ferro wrote:
> 
> Interisting reading ;) thanx for the pointers...
> 
> So far, i can setup java to handle 1.4gb ram for heap... (using the -Xms
> and -Xmx parameters)... more gives an error when creating the JVM...
> 
> Will try the -XX:+AggressiveHeap -XX:+UseLargePages tomorow... or so...
> 
> Anyway, i can assure everyone that i won't let this matter go by until it
> works on a normal machine... ;) Only now i don't have exactly the time to
> perform too much tests... (deliverables have priority for now).
> 
> ;)
> 
> LF
> 
> 
> 
> Jeremias Maerki-2 wrote:
>> 
>> Yeah, you can either buy hardware, get a different JVM or use different
>> settings (see below), or you try to figure out a way to split those
>> large page-sequences you have. I'd go for the latter. The ultimate
>> option would be to help us make FOP better to actually be able to
>> process such big page-sequences. But that's obviously a middle- to
>> long-term solution which may not be what you need. :-)
>> 
>> This might help you, too, if you have enough RAM.
>> http://java.sun.com/docs/hotspot/ism.html
>> http://java.sun.com/docs/hotspot/VMOptions.html
>> (Seems to suggest that the normal Sun JVM supports more than just 2GB of
>> heap.)
>> 
>> On 16.08.2006 14:42:36 Luis Ferro wrote:
>>> 
>>> I've read somewhere in another Java thread that the max memory one can
>>> address as "heap" is 1.8GB in a 32bit processor...
>>> 
>>> That means that the max parameter for -Xms and the like is about 1.4GB
>>> or
>>> 1.5GB...
>>> 
>>> So, if anyone still gets the message after changing the memory available
>>> in
>>> java to run fop then the only solution is to either get a JVM that
>>> doesn't
>>> have this limitation (i'm not sure that there is one, but this limit
>>> sure is
>>> crappy) or get a machine with 64bit processor!
>>> 
>>> LF
>> 
>> 
>> 
>> Jeremias Maerki
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Out-of-HEAP-memory...-tf2115067.html#a5928763
Sent from the FOP - Users forum at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to