I suppose you use a 64Bit VM right?
Which VM version do you use.
In general the OOM Exception can have several reasons, it means "out of resources" in general - not only memory.
Also you might have the problem that the GC is too slow to collect enough memory, or you have a memory leak.
In every case you should enable the gc logging, see Tuning Garbage Collection Java6
Thanks for the reply.
We are doing upgradation the below.
JDK 1.5 to JDK 1.6
JBOSS 4 to JBOSS 7.1.1 Final
Could you please advise!
GC analysis and tuning is a application specific task. For that you need to understand how the GC and the JVM heap will work. This is also different if you use a different JVM (i.e. JRockit) the link above is for the HotSpot VM which is the most used one.
So you should start with the Oracle documentation and analyse what happen to the application and the memory.
We can give you hints and a helping hand but no general solution for that
If you're on Windows your changed wrong files. You have to change or create standalone.conf.bat!
There Windows syntax has to be used, e.g.
set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M"
On wildfly/wildfly · GitHub in build/src/main/resources/bin/standalone.conf.bat you can find an example.