On 3/24/14 11:06 AM, Christopher Schultz wrote:
Do you have any idea what the cause in your particular case?
I didn't yesterday; it would be putting it mildly that there's very
little of my own code in the Tomcat context (almost all of it in a layer
that communicates with an AS/400-native
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 3/25/14, 12:00 PM, James H. H. Lampert wrote:
On 3/24/14 11:06 AM, Christopher Schultz wrote:
Do you have any idea what the cause in your particular case?
I didn't yesterday; it would be putting it mildly that there's
very little
We have noticed that after a certain amount of continuous uptime, Tomcat
eventually runs out of memory.
Now, I was always taught that the only thing that's supposed to be
capable of causing a memory leak in Java is unintended object retention.
At any rate, is there a good way specific to
From: James H. H. Lampert [mailto:jam...@touchtonecorp.com]
Subject: Detecting out-of-memory condition
We have noticed that after a certain amount of continuous uptime, Tomcat
eventually runs out of memory.
Your app has a memory leak.
At any rate, is there a good way specific to Tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 3/24/14, 1:38 PM, James H. H. Lampert wrote:
We have noticed that after a certain amount of continuous uptime,
Tomcat eventually runs out of memory.
:(
Now, I was always taught that the only thing that's supposed to be
capable of
On Mon, Mar 24, 2014 at 1:57 PM, Caldarale, Charles R
chuck.caldar...@unisys.com wrote:
From: James H. H. Lampert [mailto:jam...@touchtonecorp.com]
Subject: Detecting out-of-memory condition
We have noticed that after a certain amount of continuous uptime, Tomcat
eventually runs out
