One guess: IS being hung + heap dump being generated could very likely indicate a memory issue. In other words, your IS is using all of the heap, causing Garbage Collection to desperately run to free up resources, giving the impression that the application is hung. At some point, GC may not be able to free up enough resources, which would generate an OutOfMemoryException and that can be the reason for your heap dump being generated.
As RMG suggested, check your min/max heap settings in the setenv.[bat|sh] file to see if they’re appropriate. Also, start monitoring memory consumption of the Integration Server. The IS Statistics page could be a place to start but I recommend hooking up visualVM to the JVM instead for a more in-depth analysis.
If memory turns out to be your problem, you then need to figure out why: do you simply not have enough resources allocated or is there a leak? But we’ll cross that bridge when we get there.
Percio
#webMethods#Integration-Server-and-ESB