Lets say that you have specified some dump agents for your WebSphere JVM and you find that the *.dmp is still appearing in the <was_profile_root> Example “Generic Arguments” given to a specific JVM -verbosegc -Xdump:heap:events=gpf+user,range=1..0,file=/var/was/heapdump/heapdump.%Y%m%d.%H%M%S.%pid.phd,request=exclusive+prepwalk -Xdump:heap:events=systhrow,filter=java/lang/OutOfMemoryError,range=1..1,file=/var/was/heapdump/heapdump.%Y%m%d.%H%M%S.%pid.phd,request=exclusive+prepwalk -Xdump:java:file=/var/was/heapdump/javacore.%Y%m%d.%H%M%S.%pid.txt -Xdump:snap:file=/var/was/heapdump/snapdump.%Y%m%d.%H%M%S.%pid.trc -Xdump:system:events=gpf+abort+traceassert,file=/var/was/heapdump/javacore.%Y%m%d.%H%M%S.%pid.dmp,range=1..0,priority=999,request=serial -Xdump:what Solution is to add Xdump:none which will turn off the IBM JDK defaults. In my.. read more →

Below are some  interesting points about JVM arguments such as -xdump to control Heapdump, CoreDump, and ThreadDumps. Essentially: Heap dumps and system dumps can only be generated on platforms that make use of the IBM Java SDK: AIX, Linux, Windows. Therefore, these files cannot be generated on platforms such as Solaris and HP-UX. However, generating.. read more →