Develop Reference

Constant dspace error java.lang.OutOfMemoryError: Java heap space

I have a DSpace server, after uprading from version 4.3 to 5.1, it constantly stops working after some hours with following error:
java.lang.OutOfMemoryError: Java heap space
I've read answers to the same questions, but they didn't help me.
My JAVA_OPTS: -Xmx4096M -Xms4096M -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8
Here are my logs:
dspace.log.2015-04-21: http://jpst.it/ylU4
tomcat7-stderr.2015-04-20.log: http://jpst.it/ylTN
localhost_access_log.2015-04-20.txt: http://jpst.it/ylTT
I searched the internet for a solution and could not find one, does any one have a clue?

Your tomcat log file quite clearly says that it isn't using the JAVA_OPTS you're passing in:
INFO: Command line argument: -Xmx256m
In my experience, DSpace 5 needs at least 512MB; your 4GB look a little excessive unless your DSpace instance is very big / gets lots of traffic.
You aren't telling us what operating system you're using, so it's hard to give advice on how where to set these properly. Start with your tomcat startup script and/or the tomcat configuration files. On my Red Hat Enterprise Linux 6.6 boxes (with tomcat6), the correct place for the memory settings is /etc/tomcat6/tomcat6.conf.

Unable to start Weblogic 10.3

I am using Windows 8 Pro 64 bit, Java 1.6 64 bit. I am trying to start Weblogic with following memory args (setDomainEnv.cmd):
set USER_MEM_ARGS=-Xmx2048m -XX:PermSize=512m -XX:MaxPermSize=1024m
But i'm getting an error:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Those mermory args are required to deploy the app, so i can't lower it (physical mermory installed - 8 GB).

Combined with -Xmx512M use -d64 to make sure you're running 64-bit VM. On a 64-bit machine I thought for sure I was running 64-bit virtual machine, but no. After installing 64-bit Java the -d64 option works and -Xmx allows much larger memory sizes.
java -d64 -Xmx512M mypackage.Test
Please see the below link for more solutions...
Could not reserve enough space for object heap

I am running weblogic 81. I had min=1024 and max =1024m with 4gb or RAM. 64bit processor and 32 bit java. I tried to increase the min/max value, it did not work. So, I changed the min/max to 512m and 1024m respectively. Thn it started to work.

When i installed for first time, the SOA environment developed mode, needed to do that:set JAVA_OPTIONS=%JAVA_OPTIONS% set DEFAULT_MEM_ARGS=-Xms512m -Xmx768m set PORT_MEM_ARGS=-Xms768m -Xmx1536m But over time, it shows me the same error and tube to make the following change: set JAVA_OPTIONS=%JAVA_OPTIONS% set DEFAULT_MEM_ARGS=-Xms512m -Xmx512m set PORT_MEM_ARGS=-Xms512m -Xmx512m But I'm still not sure why this happens.

PermGen Space Issue

Environment: Windows Server 2003 x86 Intel Xeon 2.3 4gb Ram | tomcat 7.0.27 | jdk 1.7.0.25
I am facing the OutOfMemoryError. SO suggests using java options to increase the permgen space using following options
-Djava.awt.headless=true -Dfile.encoding=UTF-8 -server -Xms1536m -Xmx1536m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+DisableExplicitGC
However tomcat status page still shows the permgen memory as 64MB. Why cant it pick up the value specified in the parameters?

There is no PermGen in the status page, see this http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Introduction.
Anyways you conf seems OK
Since PermGen is a java thing (not tomcat) you should use java tools to check it, take a look at this.

As your settings seem ok, check the way you apply them: If you start tomcat via batch file, create setenv.bat with the content
CATALINA_OPTS="-Dyour-settings-from-above ... all of them"
If you start a service, you'll need to update the service configuration - as I'm not on Windows, it's a long time since I did that. Did you use the tomcatw.exe to create/configure the service? Not sure...

Java Could not reserve enough space for object heap error

I have Java7 running on 32-bit Windows and 4 GB RAM, but:
java -Xmx4G -Xms4G -jar Minecraft.jar
java -Xmx3G -Xms3G -jar Minecraft.jar
java -Xmx2G -Xms2G -jar Minecraft.jar
...still does not work. Error:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
java -Xmx1G -Xms1G -jar Minecraft.jar is working. Why?

Go to Start → Control Panel → System → Advanced system settings → advanced(tab) → Environment Variables → System Variables → New:
Variable name: _JAVA_OPTIONS
Variable value: -Xmx512M

If you go thru this IBM link on java, it says that on 32 bit windows the recommended heap size is 1.5 GB and the Maximum heap size is 1.8 GB. So your jvm does not gets initialized for -Xmx2G and above.
Also if you go thru this SO answer, clearly the DLL bindings are an issue for memory reservation changing which is no trivial task. Hence what may be recommended is that you go for 64-bit Windows and a 64-bit JVM. while it will chew up more RAM, you will have much more contiguous virtual address space.

I had this problem. I solved it with downloading 64x of the Java. Here is the link: http://javadl.sun.com/webapps/download/AutoDL?BundleId=87443

This was occuring for me and it is such an easy fix.
you have to make sure that you have the correct java for your system such as 32bit or 64bit.
if you have installed the correct software and it still occurs than goto
control panel → system → advanced system settings for Windows 8 or
control panel → system and security → system → advanced system settings for Windows 10.
you must goto the {advanced tab} and then click on {Environment Variables}.
you will click on {New} under the <system variables>
you will create a new variable. Variable name: _JAVA_OPTIONS Variable Value: -Xmx512M
At least that is what worked for me.

to make sure it runs the 64 bit version of java have it like this:
"c:\Program Files\Java\jre7\bin\java.exe" -Xmx1536M -Xms1536M -XX:MaxPermSize=256M -jar forge-1.6.4-9.11.1.965-universal.jar
take a look at what jre version you have installed just in case.. x64 should be in program files while x32 resides in Program Files (x86)

4gb RAM doesn't mean you can use it all for java process. Lots of RAM is needed for system processes.
Dont go above 2GB or it will be trouble some.
Before starting jvm just check how much RAM is available and then set memory accordingly.

this is what worked for me (yes I was having the same problem)
were is says something like java -Xmx3G -Xms3G put java -Xmx1024M
so the run.bat should look like
java -Xmx1024M -jar craftbukkit.jar -o false
PAUSE

Double click Liferay CE Server -> add -XX:MaxHeapSize=512m to Memory args -> Start server!
Enjoy...
It's work for me!

This is an old subject. But those using a stack, like Bitnami WildFly 13, should know that the stack installation has its own Java engine in \Bitnami\wildfly-13.0.0-1\java.
On Windows, the installation takes the stack Java own engine for default configurations and it starts Java with option -client, not -server, even though there is/are other Java engines installed in the system. You need to modify standalone.conf.bat to specify explicitly your Java path and add -server option along with the desired memory allocation.
Example:
set "JAVA_HOME=C:\Program Files\Java\jdk1.8.0_311”
set "JAVA_OPTS=-server -Xms2048M -Xmx4096M"
:JAVA_OPTS_SET
rem set "JAVA_HOME=C:\opt\jdk1.6.0_23\bin\java"
I hope this helps.

OutOfMemory error deploying war file in Glassfish 2.1.1 due to too much memory (-Xms -Xmx settings)

We get an error (OutOfMemory) when we deploy a war file in Glassfish 2.1.1. This is related to the memory options in the domain.xml file.
We increased the -Xmx and -Xms jvm-options settings to 1024 instead of the default 512, like this:
<jvm-options>-Xms=1024m</jvm-options>
<jvm-options>-Xmx=1024m</jvm-options>
<jvm-options>-XX:MaxPermSize=256m</jvm-options>
<jvm-options>-server</jvm-options>
<jvm-options>-D64</jvm-options>
The command we use:
asadmin deploy --user admin --passwordfile <passwd-file> --host localhost --port 4848 <warfile>
The error we got in server.log:
[#|2011-03-15T09:40:56.750+0100|SEVERE|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=15;_ThreadName=Thread-40;_RequestID=16902980-9800-488e-82b5-0104cd18e57c;|Exception occured in J2EEC Phasejava.lang.OutOfMemoryError:
com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module ...
When we change the jvm-options back to the original value (512m), the error is solved. Any clues why this is happening? Is there a maximum value for these settings?
System info
Java version: Java HotSpot(TM) Server VM (16.3-b01-jre1.6.0.07-rc1)
OS: HP-UX Itanium 64bit

You are using a 64-bit setup, but you cannot get use of the 64-bit features in total, meaning your memory usage is lacking. I found interesting post on that: http://www.java.net/node/704100
Could there be help of this tip? Tick my answer if you got some new ideas with this link :)