Resolve Java Web Application OutOfMemory
Budget: ₹12,500 – ₹37,500 INR
My Java-based web application starts cleanly, runs for several hours, then crashes with an OutOfMemoryError. The problem is clearly visible in production logs and coincides with a sudden heap spike; normal garbage-collection tuning has had no effect. I need a focused memory-profiling intervention that pinpoints the leak and delivers a sustainable fix.
Scope of work
• Capture and analyse heap dumps taken just before the crash.
• Profile the live instance (Java VisualVM, Eclipse MAT, YourKit, or similar) to trace object-retention paths.
• Identify the exact code, library, or configuration responsible for the unbounded growth.
• Implement or propose code/config changes that eliminate the leak and keep heap usage stable over long-running sessions.
• Provide a concise report summarising findings, steps taken, and validation results (before/after memory graphs, GC logs, etc.).
Acceptance criteria
– Application can run continuously for 24 h under typical production load without throwing OutOfMemoryError.
– Heap usage plateaus at an expected level with no unexplained growth in successive GC cycles.
– All changes are delivered as a clean Git patch or pull request, with notes for deployment.
Access to the repository, sample traffic generator, and current GC logs will be supplied immediately after kickoff.
Scope of work
• Capture and analyse heap dumps taken just before the crash.
• Profile the live instance (Java VisualVM, Eclipse MAT, YourKit, or similar) to trace object-retention paths.
• Identify the exact code, library, or configuration responsible for the unbounded growth.
• Implement or propose code/config changes that eliminate the leak and keep heap usage stable over long-running sessions.
• Provide a concise report summarising findings, steps taken, and validation results (before/after memory graphs, GC logs, etc.).
Acceptance criteria
– Application can run continuously for 24 h under typical production load without throwing OutOfMemoryError.
– Heap usage plateaus at an expected level with no unexplained growth in successive GC cycles.
– All changes are delivered as a clean Git patch or pull request, with notes for deployment.
Access to the repository, sample traffic generator, and current GC logs will be supplied immediately after kickoff.