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 a
JVM problem with SCO's implementation, but unfortunately, there's nothing I
can do about that, <sarcasm>SCO being such an awesome
implementation</sarcasm>. I was hoping that someone could say something
like, "oh yeah, JBoss does <whatever> at about that time", and I'd have a
place to go to try to make a temporary workaround in the JBoss code. It
could be that the JVM is doing something itself, but if so, it's still
related somehow to JBoss (or Tomcat, I suppose), since we have other Java
programs that run longer than 395 minutes.
But thanks again for the try!
Jim
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [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 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.
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
