Hello Ashish,
Jvm crashes has to do with a defect/bug in the jvm as it is not suppose to crash under any circumstance, therefore you should open a suppor ticket with the jvm provider.
In the meantime, you could try:
1. Use an alternate JVM (Sun Java 6 beta, IBM jdk, etc).
2. Configure the Appserver with -Xbootclasspath instead of -javaagent switch.
3. Disable SQLAgent by removing the AGENT_HOME/ext/SQLAgent.jar out of the AGENT directory - the problem could be related to a metric explosion.
4.Disable Platform monitor: move the following files from the /wily/ext directory to another directory.
As far as I know, PM component it is the only one that could make native calls and could possible cause this issue, but I doubt.
5. For testint purpose, disable JMX collection. Set introscope.agent.jmx.enable=false
Polling lots of JMX metrics is CPU intensive. If possible, set for now introscope.agent.jmx.enable=false
6. Find out if the problematic server is at the same OS level patch as the other similar setups (LABS).
Kindly understand that this is an underlying JVM problem and there is not much we can do from our end to fix this, other than suggesting the above workarounds.
Regards,
Sergio