UI config hangs if an OOM is generated during config load - should catch and report gracefully

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.6.0
  • Fix Version/s: None
  • Component/s: UI
  • Labels:
    None

Description

UI config hangs (doesnt return to browser ever) if an OOM is generated during config load - should catch and report gracefully

ideally it would be nice to report the system config (java memory) during UI operations, this would also aid us catching memory leaks..

Activity

Hide
Permalink
Andrea Aime added a comment -

Rob, I don't think we can put catch(Error) everywhere in the code to catch memory leaks, but I'm wondering, aren't errors like that reported anyways?
Moreover, you know that OOM did not use to generate a stack trace, and that started happening only with java6? (so you need to run on a java6
VM to have the reports).
Anywyas, if you have a patch I'll gladly have a look at it.
Also, to debug OOM I usually use YourKit, we have 10 licenses for people working on GeoServer, want one?

Show
Andrea Aime added a comment - Rob, I don't think we can put catch(Error) everywhere in the code to catch memory leaks, but I'm wondering, aren't errors like that reported anyways? Moreover, you know that OOM did not use to generate a stack trace, and that started happening only with java6? (so you need to run on a java6 VM to have the reports). Anywyas, if you have a patch I'll gladly have a look at it. Also, to debug OOM I usually use YourKit, we have 10 licenses for people working on GeoServer, want one?

People

  • Assignee:
    Andrea Aime
    Reporter:
    Rob Atkinson
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: