Technical Blog Post
Abstract
OutOfMemory errors while deploying applications in WebSphere Application Server
Body
When running application deployments in WebSphere Application Server, if you encounter a failure such as ADMA5069E: The installation of application <AppName> failed in SystemOut.log of the deployment manager, there is high probability that, wsadmin command has ended in an OutOfMemory. Application deployments to WebSphere Application Server is performed via the wsadmin command.
To troubleshoot this,
Verify if your wsadmin JVM options are defaults, if yes they may be insufficient for deploy large EAR files. wsadmin command located under <WAS-InstallDir>/bin/wsadmin.sh|bat is where you should look for depending on your operating environment.
By default here are the JVM settings
# Set java options for performance
PLATFORM=`/bin/uname`
case $PLATFORM in
AIX)
PERF_JVM_OPTIONS="-Xms256m -Xmx256m -Xquickstart" ;;
Linux)
PERF_JVM_OPTIONS="-Xms256m -Xmx256m -Xquickstart" ;;
SunOS)
PERF_JVM_OPTIONS="-Xms256m -Xmx256m -XX:MaxPermSize=128m" ;;
HP-UX)
PERF_JVM_OPTIONS="-Xms256m -Xmx256m -XX:MaxPermSize=128m" ;;
OS/390)
PERF_JVM_OPTIONS="-Xms256m -Xmx256m" ;;
You can either edit the parameters indicated above to do a permanent setting of recommended heap values for all future deployments or, if you do not wish to edit the script file, you have an additional way of passing JVM arguments for each issue of the wsadmin command.
Look at the example below:
wsadmin.sh -javaoption -Xms512m -Xmx4096m -lang jython -username wasadmin -password was1Admin -f /tmp/deploy_MY_ear.jy '
Tip:
If your problem is not related to heap size or OutOfMemory but still the wsadmin command fails, you have an option to enable trace for the wsadmin command. For instructions refer
UID
ibm11124577