0:54 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] What happens at 6 hours and 35 minutes?
>
>
> You might also try sucking down as much memory outside the process as
> possible to see if that is an issue as well.
>
> --- Jim Brownfield <[EMAIL PROTECTE
]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Matthew
> > Hixson
> > Sent: Wednesday, May 02, 2001 10:23 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: [JBoss-user] What happens at 6 hours and 35 minutes?
> >
> >
> > On Wed, 2 May 2001, Jim Brownfield
Ohhh, thanks, that might work!
Jim
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Matthew
> Hixson
> Sent: Wednesday, May 02, 2001 10:23 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] What happens at 6 hours and 35
On Wed, 2 May 2001, Jim Brownfield wrote:
> Thanks for the suggestions, Robert. I'll give that a try on the next pass.
> At 6 hours a shot, I don't get very many tries during a day! :( Currently,
> I've turned off the JIT (I've got a couple more hours to see if that
> worked). For what I want
sday, May 02, 2001 7:37 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-user] What happens at 6 hours and 35 minutes?
>
>
>
> Not sure whether this will help, but here are a couple of
> suggestions ... Write a thread which dumps memory usage,
> calls System.gc() and dum
ling didn't provide anything useful.
>
> Thanks again!
> Jim
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of
> Toby Allsopp
> > Sent: Wednesday, May 02, 2001 3:01 PM
> > To: [EMAIL PROTEC
gt; From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Toby Allsopp
> Sent: Wednesday, May 02, 2001 3:01 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] What happens at 6 hours and 35 minutes?
>
>
> On Wed, May 02, 2001 at 02:42:43PM -0700, Jim Brownfield
On Wed, May 02, 2001 at 02:42:43PM -0700, Jim Brownfield wrote:
> Thanks for the suggestion, but it's not 6:35A.M, it's 6 hours and 35 minutes
> running time, and it doesn't matter when I start JBoss, but you can set your
> clock by when the JVM will fail after you've started it. I'm sure there's
ECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Coleman
> Sent: Wednesday, May 02, 2001 12:28 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] What happens at 6 hours and 35 minutes?
>
>
> >
> > Consistently, JBoss causes the JVM 1.2.2_001 on SCO Openserv
>
> Consistently, JBoss causes the JVM 1.2.2_001 on SCO Openserver to crash with
> a "Memory Fault" at 6 hours and 35 minutes (395 minutes, 23,700 seconds).
>
> Anybody have any ideas?
>
Does your system run any cron jobs at 06:35?
If it does, that would be the place to start.
__
On Wed, May 02, 2001 at 10:49:00AM -0700, Jim Brownfield wrote:
>
> Consistently, JBoss causes the JVM 1.2.2_001 on SCO Openserver to crash with
> a "Memory Fault" at 6 hours and 35 minutes (395 minutes, 23,700 seconds).
> I've looked at numerous parameters in the config files, and I've been
> lo
11 matches
Mail list logo