This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
We have deployed our application to a server in which JVM is crashing many, many times there are lot of heap dumps getting created in WebSphere6. In fact, our application's JVM is crashing every few minutes, creating 120MB dumps each time. Clearly there is something wrong with the application that needs to be addressed and until the app JVM crash issue is corrected, the WAS filesystem will continue to fill, causing problems with deployments and general WAS sanity.
If heapdumps are getting created and JVM is getting crashed everytime on server. Does this behavior should happen to me locally i.e development box? If locally, not able to produce. How do i handle this issue?
The server may be crashing due to a use-case not being replicated on the local system.
You can generate thread dumps when a crash is imminent. This may help identify the code causing the server crash.
If you are going to generate a thread dump, a nice procedure to analyze is generate multiple dumps between small intervals and determine if any thread is in the same code in all the dumps. This code could then point to the issue.