From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
When our java application server runs, after a certain amount of
activity it eventually throws an OutOfMemory exception and dies. This
only happens on the ia64 platform (the same application is fine on
ia32) and only on Update3 (the application runs fine on Update2 of RHEL3).
I'm still trying to formulate a simpler case than our entire java
application, but so far we haven't been able to reproduce it more simply.
Object tracing seems to indicate that garbage collection occurs
correctly, so I don't understand what exactly is causing the out of
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start LifeKeeper java GUI server
2. Begin administration of the server
3. wait for the crash
Actual Results: Java server throws OutOfMemory exception
Expected Results: Server should operate with no exceptions
Can you try mtracing the application?
I.e. run it under debugger with MALLOC_TRACE=/tmp/app.mtrace in the environment,
put a breakpoint on java's main, call mtrace () there and continue.
Then run mtrace utility on the log file to see whether there are any memory
leaks and where.
If this doesn't show anything, we need a (small) reproducer.
If you have details, please reopen.