Memory Error installing IBM IIS 8.0.1 FixPack 2

[myukassign]

I am posting this blog after a lot of search on the net and dsexchage. I am getting java out of memory exception while installing 8.0.1 Fix pack 2.

I could see a known issue in the Release note that sometimes it may throw out of memory exception but to resolve that they have given some steps. Even after I followed the steps, restarted the server still the same error . Any help, any one resolved this issue. Please see below the steps given in the fix pack installation guide.


Fix pack installation fails with OutOfMemory exception in WebSphere Application Server

1. Log in to the WebSphere administrative console as the WebSphere administrator.
2. In the topology tree, expand Servers and click Application Servers.
3. Click the server1 link (where server1 is the name of the application server that you want to configure).
4. Under Server Infrastructure, expand Java and Process Management.
5. Click Process Definition.
6. Under the Additional Properties section, click Java Virtual Machine.
7. In the Maximum Heap Size field, type 1280.
8. Click Apply or OK.
9. Install the patch.
10. Reset the value of Maximum Heap Size to your original value after you install the patch.


The error I am getting is


bash-3.00# ./Updater -i /opt/IBM/InformationServer
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...JVMDG318: Heap dump file written to /opt/IBM/FixPack2/heapdump467196.1283771800.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /opt/IBM/FixPack2/javacore467196.1283771802.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...JVMDG318: Heap dump file written to /opt/IBM/FixPack2/heapdump467196.1283771805.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /opt/IBM/FixPack2/javacore467196.1283771807.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...JVMDG318: Heap dump file written to /opt/IBM/FixPack2/heapdump467196.1283771811.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /opt/IBM/FixPack2/javacore467196.1283771813.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
Exception occurred during event dispatching:
java.lang.OutOfMemoryError
bash-3.00# ./Updater -i /opt/IBM/InformationServer
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...JVMDG318: Heap dump file written to /opt/IBM/FixPack2/heapdump585752.1283773034.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /opt/IBM/FixPack2/javacore585752.1283773036.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
Exception occurred during event dispatching:
java.lang.OutOfMemoryError
at java.io.UnixFileSystem.resolve(UnixFileSystem.java(Compiled Code))
at java.io.File.<init>(File.java(Inlined Compiled Code))
at java.io.File.listFiles(File.java(Inlined Compiled Code))
at com.ibm.is.install.core.pm.UVInstance.searchFile(UVInstance.java(Compiled Code))
at com.ibm.is.install.core.pm.UVInstance.searchFile(UVInstance.java(Compiled Code))
at com.ibm.is.install.core.pm.UVInstance.searchProjects(UVInstance.java:564)
at com.ibm.is.install.core.pm.UVInstance.getFileArrayLocal(UVInstance.java:539)
at com.ibm.is.install.core.pm.UVAction.getFileActionArray(UVAction.java:171)

[ray.wurlod]

What are the ulimit settings for the user performing the installation?

Most of them need to be set to "unlimited". There are other considerations on AIX that need to be considered, such as the LDR_CNTRL environment variable (treatment differs on 32-bit vs 64-bit environments).