Bug #2843
closed
Rudder can fail to generate promises when Java is lacking memory
Description
Just before jetty fails, the webapp log diplayed this:
[...] ERROR net.liftweb.http.LiftRules - Exception being returned to brower when procesing Req(List(F99....,_) Map(F9... -> List(99...), _ -> List (13..)), ParsePAth(List(comet_request, 95..., 7o9..., F9...), , true, false), /rudder, GetRequest, Empty [...] java.lang.NullPointerException: null [...] GetServerName [...]
And the /var/log/rudder/ldap/slapd.log diplayed messages about indexes:
[...] (osName) is not indexed (osVersion) is not indexed (osServicePack) is not indexed [...]
Updated by Nicolas CHARLES about 12 years ago
This is clearly not normal !
We need some metric on what takes time and what does not. Running the application in debug mode would help understand which part of the deploiement takes too much time
Updated by Jonathan CLARKE about 12 years ago
- Category set to Architecture - Code maintenance
- Status changed from New to Discussion
- Target version changed from 2.4.0~beta4 to 24
We have established that this was caused by not enough memory allocated to the JVM. Changing XmX and XmS options to java fixed this issue... but we still have a memory mangement problem. Should this be merged with #2813?
Updated by Jonathan CLARKE about 12 years ago
- Subject changed from Rudder can't generate promises and jetty fails after 18mins of generation process to Rudder can fail to generate promises when Java is lacking memory
Updated by Nicolas CHARLES over 11 years ago
I guess this is either not targeted to 2.5, nor relevant any more
With correct configuration (meaning, enough ram) the problem didn't happen again, and Rudder 2.6 provides significant lower memory usage
Shall I reject this ?
Updated by Jonathan CLARKE over 11 years ago
Nicolas CHARLES wrote:
I guess this is either not targeted to 2.5, nor relevant any more
With correct configuration (meaning, enough ram) the problem didn't happen again, and Rudder 2.6 provides significant lower memory usageShall I reject this ?
Well, using less memory is a good way to avoid the problem, but I think the main issue here is that it is totally unclear what is going on.
Is there any way you can detect "OutOfMemory", and log a clearer error message?
Updated by François ARMAND over 11 years ago
- Target version changed from 24 to Ideas (not version specific)
Updated by Nicolas CHARLES almost 11 years ago
Interestingly, we could suicide the web interface on OOM:
http://stackoverflow.com/questions/12096403/java-shutting-down-on-out-of-memory-error
Updated by François ARMAND over 8 years ago
- Related to User story #5617: Detecting and restarting Rudder on OOM (Out Of Memory Exception) added
Updated by François ARMAND over 7 years ago
- Status changed from Discussion to Rejected
I'm closing that one because there is much more information in #5617
Updated by François ARMAND over 5 years ago
- Related to Bug #14281: Manage rudder webapp shutdown correctly in case of fatal exception at startup added