You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Ian Hunter <ih...@informiam.com> on 2007/07/19 16:14:48 UTC

Strange memory problems / white screens

We've noticed a problem where intermittently Geronimo starts failing to
respond to web requests (browser symptom is a blank white screen) - when
this starts happening, we notice that on the system info tab, the memory
metrics display "Not Yet Available" but after we restart Geronimo
completely, web requests work and the memory values display.

 

Has anyone else seen anything like this?

 

_______________________________
Ian Hunter
Solution Architect

925 Northpoint Parkway, Suite 430
Alpharetta, GA 30005

678.990.7416 office
770.754.4264 fax
404.314.8693 mobile

 


Re: Strange memory problems / white screens

Posted by Peter Petersson <pe...@pmb.mine.nu>.
Ian Hunter wrote:
>
> This is Geronimo 1.1.1 running on Window (!!!) JDK 1.5.0_11 -- there 
> **was** Apache running mod_jk but I took it out of the loop using 
> ProxyPass/ProxyPassReverse.  There are a small handful of apps (one 
> EAR, maybe 3 WARs) on the server.
>
Okey having that cleared up I suspect the problem to be with some of the 
deployed apps G 1.1.1 is in my opinion quite stable and I haven't heard 
about any problems with your version of (sun:s) JDK.
Some multi threaded configurations of Apache with older versions of 
mod_jk (check the mod_jk log for connection losses) is known to cause 
problems leading to memory leaks and problems like the one you describe 
but if you still have this problem it is probably not be the case.
>
>  
>
> We're starting to monitor memory usage more closely, but after the 
> problem occurs, we can't see memory usage -- we get that "Not Yet 
> Available" message.
>
I would try Kevan:s suggestion and also if you have the equivalent to 
unix "tail -f geronimo.log" ("live" logging) in windows it may help in 
narrowing the offender.
regards
  Peter Petersson
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* Peter Petersson [mailto:peter@pmb.mine.nu]
> *Sent:* Thursday, July 19, 2007 11:15 AM
> *To:* user@geronimo.apache.org
> *Subject:* Re: Strange memory problems / white screens
>
>  
>
> Someone is probably going to as you this so I might as well ;)
>
> What version of Geronimo are you running ?
> What jdk version?
> Is there a Apache server involved via mod_jk ?
> Is it one G deployed application in particular that you notice the 
> problem in?
> Is there other G deployed apps?
>  
>
> At my work we run a G v1.1.1 server and have several Geronimo deployed 
> applications with occasionally somewhat heavy load without any memory 
> leaks in G (months of uptime) so if this is the version you are using 
> I would start looking at the deployed applications memory handling.
> Is there a steady increase of memory usage?  you can look at the 
> Information page to keep track at it. If this is the case some of your 
> deployed applications may leak memory as the garbage collector cant 
> release some resources (like open database connections holding on to 
> it), tailing good logging output could help locating the problem.
>
> regards
>    Peter Petersson
>  
>
> Ian Hunter wrote:
>
> We've noticed a problem where intermittently Geronimo starts failing 
> to respond to web requests (browser symptom is a blank white screen) 
> -- when this starts happening, we notice that on the system info tab, 
> the memory metrics display "Not Yet Available" but after we restart 
> Geronimo completely, web requests work and the memory values display.
>
>  
>
> Has anyone else seen anything like this?
>
>  
>
> _______________________________
> **Ian Hunter**
> **Solution Architect**
>
> 925 Northpoint Parkway, Suite 430
> Alpharetta, GA 30005
>
> 678.990.7416 **office**
> 770.754.4264 **fax**
> 404.314.8693 **mobile**
>
>  
>
>  
>


RE: Strange memory problems / white screens

Posted by Ian Hunter <ih...@informiam.com>.
This is Geronimo 1.1.1 running on Window (!!!) JDK 1.5.0_11 - there *was*
Apache running mod_jk but I took it out of the loop using
ProxyPass/ProxyPassReverse.  There are a small handful of apps (one EAR,
maybe 3 WARs) on the server.

 

We're starting to monitor memory usage more closely, but after the problem
occurs, we can't see memory usage - we get that "Not Yet Available" message.

 

  _____  

From: Peter Petersson [mailto:peter@pmb.mine.nu] 
Sent: Thursday, July 19, 2007 11:15 AM
To: user@geronimo.apache.org
Subject: Re: Strange memory problems / white screens

 

Someone is probably going to as you this so I might as well ;)

What version of Geronimo are you running ?
What jdk version?
Is there a Apache server involved via mod_jk ?
Is it one G deployed application in particular that you notice the problem
in? 
Is there other G deployed apps?
 

At my work we run a G v1.1.1 server and have several Geronimo deployed
applications with occasionally somewhat heavy load without any memory leaks
in G (months of uptime) so if this is the version you are using I would
start looking at the deployed applications memory handling. 
Is there a steady increase of memory usage?  you can look at the Information
page to keep track at it. If this is the case some of your deployed
applications may leak memory as the garbage collector cant release some
resources (like open database connections holding on to it), tailing good
logging output could help locating the problem.

regards 
   Peter Petersson
  

Ian Hunter wrote: 

We've noticed a problem where intermittently Geronimo starts failing to
respond to web requests (browser symptom is a blank white screen) - when
this starts happening, we notice that on the system info tab, the memory
metrics display "Not Yet Available" but after we restart Geronimo
completely, web requests work and the memory values display.

 

Has anyone else seen anything like this?

 

_______________________________
Ian Hunter
Solution Architect

925 Northpoint Parkway, Suite 430
Alpharetta, GA 30005

678.990.7416 office
770.754.4264 fax
404.314.8693 mobile

 

 


Re: Strange memory problems / white screens

Posted by Peter Petersson <pe...@pmb.mine.nu>.
Someone is probably going to as you this so I might as well ;)

What version of Geronimo are you running ?
What jdk version?
Is there a Apache server involved via mod_jk ?
Is it one G deployed application in particular that you notice the 
problem in?
Is there other G deployed apps?
 

At my work we run a G v1.1.1 server and have several Geronimo deployed 
applications with occasionally somewhat heavy load without any memory 
leaks in G (months of uptime) so if this is the version you are using I 
would start looking at the deployed applications memory handling.
Is there a steady increase of memory usage?  you can look at the 
Information page to keep track at it. If this is the case some of your 
deployed applications may leak memory as the garbage collector cant 
release some resources (like open database connections holding on to 
it), tailing good logging output could help locating the problem.

regards
   Peter Petersson
 

Ian Hunter wrote:
>
> We've noticed a problem where intermittently Geronimo starts failing 
> to respond to web requests (browser symptom is a blank white screen) 
> -- when this starts happening, we notice that on the system info tab, 
> the memory metrics display "Not Yet Available" but after we restart 
> Geronimo completely, web requests work and the memory values display.
>
>  
>
> Has anyone else seen anything like this?
>
>  
>
> _______________________________
> **Ian Hunter**
> **Solution Architect**
>
> 925 Northpoint Parkway, Suite 430
> Alpharetta, GA 30005
>
> 678.990.7416 **office**
> 770.754.4264 **fax**
> 404.314.8693 **mobile**
>
>  
>


Re: Strange memory problems / white screens

Posted by Peter Petersson <pe...@pmb.mine.nu>.
Ian Hunter wrote:
>
> Where do I find the output from --verbose:gc -- I don't see anything 
> new in geronimo.log.
>
The output should be in var/log/geronimo.out (its located alongside with 
geronimo.log) or it may be printed in the console depending on the 
method you use to start the server.

regards
   Peter Petersson
>
>  
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* Kevan Miller [mailto:kevan.miller@gmail.com]
> *Sent:* Thursday, July 19, 2007 10:41 AM
> *To:* user@geronimo.apache.org
> *Subject:* Re: Strange memory problems / white screens
>
>  
>
>  
>
> On Jul 19, 2007, at 10:14 AM, Ian Hunter wrote:
>
>
>
> We've noticed a problem where intermittently Geronimo starts failing 
> to respond to web requests (browser symptom is a blank white screen) 
> -- when this starts happening, we notice that on the system info tab, 
> the memory metrics display "Not Yet Available" but after we restart 
> Geronimo completely, web requests work and the memory values display.
>
>  
>
> Has anyone else seen anything like this?
>
>  
>
> Hi Ian,
>
> Any errors showing up in var/log/geronimo.log? Is this behavior truly 
> intermittent or somewhat predictable? I would suspect that you have a 
> memory leak... Have you tracked memory utilization?
>
>  
>
> I've found the following useful:
>
>  
>
> export JAVA_OPTS=" -verbose:gc -XX:+PrintGCDetails 
> -XX:+HeapDumpOnOutOfMemoryError"
>
>  
>
> First two options will cause GC statistics to be printed by the JVM.
>
>  
>
> HeapDumpOnOutOfMemoryError will cause a heap dump to be created on 
> OOME conditions. Very handy for post-mortem analysis... There's no 
> overhead associated with this setting (only pay a cost when you run 
> out of memory). 
>
>  
>
> --kevan 
>


RE: Strange memory problems / white screens

Posted by Ian Hunter <ih...@informiam.com>.
Where do I find the output from -verbose:gc - I don't see anything new in
geronimo.log.

 

 

  _____  

From: Kevan Miller [mailto:kevan.miller@gmail.com] 
Sent: Thursday, July 19, 2007 10:41 AM
To: user@geronimo.apache.org
Subject: Re: Strange memory problems / white screens

 

 

On Jul 19, 2007, at 10:14 AM, Ian Hunter wrote:





We've noticed a problem where intermittently Geronimo starts failing to
respond to web requests (browser symptom is a blank white screen) - when
this starts happening, we notice that on the system info tab, the memory
metrics display "Not Yet Available" but after we restart Geronimo
completely, web requests work and the memory values display.

 

Has anyone else seen anything like this?

 

Hi Ian,

Any errors showing up in var/log/geronimo.log? Is this behavior truly
intermittent or somewhat predictable? I would suspect that you have a memory
leak... Have you tracked memory utilization?

 

I've found the following useful:

 

export JAVA_OPTS=" -verbose:gc -XX:+PrintGCDetails
-XX:+HeapDumpOnOutOfMemoryError"

 

First two options will cause GC statistics to be printed by the JVM.

 

HeapDumpOnOutOfMemoryError will cause a heap dump to be created on OOME
conditions. Very handy for post-mortem analysis... There's no overhead
associated with this setting (only pay a cost when you run out of memory). 

 

--kevan 


Re: Strange memory problems / white screens

Posted by Kevan Miller <ke...@gmail.com>.
On Jul 19, 2007, at 10:14 AM, Ian Hunter wrote:

> We’ve noticed a problem where intermittently Geronimo starts  
> failing to respond to web requests (browser symptom is a blank  
> white screen) – when this starts happening, we notice that on the  
> system info tab, the memory metrics display “Not Yet Available” but  
> after we restart Geronimo completely, web requests work and the  
> memory values display.
>
>
>
> Has anyone else seen anything like this?

Hi Ian,
Any errors showing up in var/log/geronimo.log? Is this behavior truly  
intermittent or somewhat predictable? I would suspect that you have a  
memory leak... Have you tracked memory utilization?

I've found the following useful:

export JAVA_OPTS=" -verbose:gc -XX:+PrintGCDetails -XX: 
+HeapDumpOnOutOfMemoryError"

First two options will cause GC statistics to be printed by the JVM.

HeapDumpOnOutOfMemoryError will cause a heap dump to be created on  
OOME conditions. Very handy for post-mortem analysis... There's no  
overhead associated with this setting (only pay a cost when you run  
out of memory).

--kevan