Greg Lappen wrote:
That's a good idea, I'm going to try that. Its a cheap way to confirm
or deny my suspicions.
Thanks!
On Dec 21, 2004, at 9:20 AM, Eric Rotick wrote:
I've not tried this myself but you could add a Runtime.addShutdownHook
and get it to print out anything which will give you a c
I'd be interested to know the outcome of this one when you crack it.
On Tue, 21 Dec 2004 09:32:42 -0500, Greg Lappen <[EMAIL PROTECTED]> wrote:
> That's a good idea, I'm going to try that. Its a cheap way to confirm
> or deny my suspicions.
>
> Thanks!
> On Dec 21, 2004, at 9:20 AM, Eric Rotick
That's a good idea, I'm going to try that. Its a cheap way to confirm
or deny my suspicions.
Thanks!
On Dec 21, 2004, at 9:20 AM, Eric Rotick wrote:
I've not tried this myself but you could add a Runtime.addShutdownHook
and get it to print out anything which will give you a clue.
On Tue, 21 Dec
I've not tried this myself but you could add a Runtime.addShutdownHook
and get it to print out anything which will give you a clue.
On Tue, 21 Dec 2004 08:47:49 -0500, Greg Lappen <[EMAIL PROTECTED]> wrote:
> Well, turns out the RAM is fine in the server. Our hosting provider
> tested it last ni
Well, turns out the RAM is fine in the server. Our hosting provider
tested it last night and said it checked out fine. Is there any other
reason that the JVM/Tomcat would just exit like this? Could
System.exit() be called somewhere? Isn't there a way to prevent
System.exit() from being call
The application receives data packets from acoustic sensors. While the
total load is not huge, because of the way the data is collected there
are periods of no activity and then periods when all hell breaks
loose. This happens every 15 minutes and we size the memory based on
the use of swap over a
No core dump and nothing significant in the log files. The process
just went away. Actually now I think about it we did have some other
weirdness like JARs that were corrupt that also went away with the
good memory.
On Mon, 20 Dec 2004 15:13:35 -0500, Greg Lappen <[EMAIL PROTECTED]> wrote:
> When
Greg Lappen wrote:
What kind of load does your application handle? I am not processing a
HUGE amount of requests, but we server about 6000 visitors a day, 15,000
pages.
Greg
On Dec 20, 2004, at 1:28 PM, Wade Chandler wrote:
Greg Lappen wrote:
Hello-
Has anyone had a problem with Tomcat 5.0.28 c
What kind of load does your application handle? I am not processing a
HUGE amount of requests, but we server about 6000 visitors a day,
15,000 pages.
Greg
On Dec 20, 2004, at 1:28 PM, Wade Chandler wrote:
Greg Lappen wrote:
Hello-
Has anyone had a problem with Tomcat 5.0.28 crashing on Linux wi
When you say the problem was similar, did you also have no core dump or
log messages, just a missing JVM process? I am asking our hosting
provider to test the server's RAM - I was going to do this before but
since no other process ever crashes (Apache, MySql, etc.) we didn't
think it could be
I had a similar problem with an almost identical setup to yours which
turned out to be bad memory. An extra 1GB stick was added which had a
bad section in the top of the memory map. This memory only got used
when things got busy so everyone suspected some threading issue. We
got lucky and spotted s
Greg Lappen wrote:
Hello-
Has anyone had a problem with Tomcat 5.0.28 crashing on Linux with no
error messages?
My production server running with JDK 1.4.2_06, RedHat EL 3.0 just
crashes, no core dump, no errors in catalina.out, no clues. Sometimes
it goes for days, sometimes it happens severa
Hello-
Has anyone had a problem with Tomcat 5.0.28 crashing on Linux with no
error messages?
My production server running with JDK 1.4.2_06, RedHat EL 3.0 just
crashes, no core dump, no errors in catalina.out, no clues. Sometimes
it goes for days, sometimes it happens several times in one day.
13 matches
Mail list logo
