This content has been marked as final. Show 5 replies
Please try with the following modifications:
Also verify if all the mentioned paths are vaild.
i'm in the same error
how can i do this modifications?
i'm in the same error, how can i modify this parametres??
you can go to bin folder present in the domain folder and modify setDomainEnv.sh if even your admin is not running. If you do not want to touch the scripts and your admin is running, you can login into admin console go to servers -> select the server -> general -> remote start -> in the memory arguments you can add them.
I have 12Gb on a 64-bit Windows7 and 4Gb on 32-bit XP.
For the 32-bit OS - you cannot go over 1908 ~ 2GB per process, So I usually run with 1536 to be compatible with 32 or 64 bit OS's.
Just a not that the size of RAM on the machine besides the 2GB 32/64 limit has not much bearing on the JVM because I can run out of Heap even with 12GB.
Also note that most 32-bit software will take twice as much ram on a 64 bit os because of the doubling in word size - therefore applications that used to run with 768 will need 1536 on a 64 bit OS.
Try running jconsole.exe against your JVM - you will see the spike in heap usage that occurs just before your OOM error.
For example, see the following scenario triaged with JConsole.