RE: [JBoss-user] What happens at 6 hours and 35 minutes?
Thanks! Another good suggestion, but I think I've found a workaround. I disabled the JIT compiler on SCO Openserver's JVM, and JBoss has been running successfully since (albeit slower). For now, the speed decrease is not a problem (I think! ;) ). We will be porting to Linux as soon as we get device drivers for some of the hardware we use. Then, hopefully, software development in general won't feel like a constant fight for your life, and in particular, we will be able to successfully deploy a fully-functional, speedy, JBoss implementation. Can you tell that the last few years of developing on SCO have taken their toll! :) Well, back to work while I wait for SCO to bite me in the rear again... > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Grim > Shieldsson > Sent: Thursday, May 03, 2001 10: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 PROTECTED]> wrote: > > 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 minutes? > > > > > > > > > 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 to do now, the loss in performance > > > probably won't > > > > be too much of a problem, and when we are able to port to Linux > > in a few > > > > months the problem should go away. > > > > > > Hi Jim, > > > If I were dealing with this problem I would bump the system time > > into > > > the future about 6 hours just to see what happens. Good luck. > > > -M@ > > > > > > > > > ___ > > > 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 > > > = > Grim Shieldsson (James A Barrows) > Acting Chieftain of Clan StormWolf > Barbarian Freehold Alliance > Oppurtunity doesn't knock. It only presents itself after you > kick down the door. > --Kyle Chandler > > __ > Do You Yahoo!? > Yahoo! Auctions - buy the things you want at great prices > http://auctions.yahoo.com/ > > ___ > 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
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 PROTECTED]> wrote: > 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 minutes? > > > > > > 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 to do now, the loss in performance > > probably won't > > > be too much of a problem, and when we are able to port to Linux > in a few > > > months the problem should go away. > > > > Hi Jim, > > If I were dealing with this problem I would bump the system time > into > > the future about 6 hours just to see what happens. Good luck. > > -M@ > > > > > > ___ > > 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 = Grim Shieldsson (James A Barrows) Acting Chieftain of Clan StormWolf Barbarian Freehold Alliance Oppurtunity doesn't knock. It only presents itself after you kick down the door. --Kyle Chandler __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] What happens at 6 hours and 35 minutes?
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 minutes? > > > 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 to do now, the loss in performance > probably won't > > be too much of a problem, and when we are able to port to Linux in a few > > months the problem should go away. > > Hi Jim, > If I were dealing with this problem I would bump the system time into > the future about 6 hours just to see what happens. Good luck. > -M@ > > > ___ > 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
RE: [JBoss-user] What happens at 6 hours and 35 minutes?
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 to do now, the loss in performance probably won't > be too much of a problem, and when we are able to port to Linux in a few > months the problem should go away. Hi Jim, If I were dealing with this problem I would bump the system time into the future about 6 hours just to see what happens. Good luck. -M@ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] What happens at 6 hours and 35 minutes?
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 to do now, the loss in performance probably won't be too much of a problem, and when we are able to port to Linux in a few months the problem should go away. Thanks again! Jim > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Robert > Schulz > Sent: Wednesday, 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 dumps the time it takes into a file > every 10 seconds or so. This might tell you whether the > gc makes the JVM die. Next step is to implement a "state logging" > singelton into which you call whenever you enter/leave "suspect > parts" of the code and make the thread dump the state as well > continously ... this might help to narrow it down. > > Does the crash depend on load, is it always after thye _exact_ > same amount of time? > > Overall yours is a pretty nasty problem, as you'll have to > wait 6 hours to see whether it makes a difference |-( > > Good luck. > > R. > > -Original Message----- > > From: Jim Brownfield [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, May 03, 2001 8:52 > > To: [EMAIL PROTECTED] > > Subject: RE: [JBoss-user] What happens at 6 hours and 35 minutes? > > > > > > Thanks, Toby. > > > > There's no backtrace on the threads, just the typical "Memory > > fault: core > > dumped" message. I will try the kill -SIGQUIT, and see if > > that gives any > > insight. The java profiling 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 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 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 a > > > > JVM problem with SCO's implementation, but unfortunately, > > > there's nothing I > > > > can do about that, SCO being such an awesome > > > > implementation. I was hoping that someone > > could say something > > > > like, "oh yeah, JBoss does 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. > > > > > > Ok, I'll make a more helpful effort than "fix JVM". > > > > > > When the JVM crashes, does it dump stacktraces for the running > > > threads? I've > > > seen many JVMs do this, and it might give you a clue as to > > what's going on > > > at the time. > > > > > > You could also try taking thread dumps (kill -3) up until > > the time when it > > > crashes. > > > > > > Toby. > > > > > > ___ > > > 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 > > > > ___ > 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
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 dumps the time it takes into a file every 10 seconds or so. This might tell you whether the gc makes the JVM die. Next step is to implement a "state logging" singelton into which you call whenever you enter/leave "suspect parts" of the code and make the thread dump the state as well continously ... this might help to narrow it down. Does the crash depend on load, is it always after thye _exact_ same amount of time? Overall yours is a pretty nasty problem, as you'll have to wait 6 hours to see whether it makes a difference |-( Good luck. R. > -Original Message- > From: Jim Brownfield [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 03, 2001 8:52 > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] What happens at 6 hours and 35 minutes? > > > Thanks, Toby. > > There's no backtrace on the threads, just the typical "Memory > fault: core > dumped" message. I will try the kill -SIGQUIT, and see if > that gives any > insight. The java profiling 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 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 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 a > > > JVM problem with SCO's implementation, but unfortunately, > > there's nothing I > > > can do about that, SCO being such an awesome > > > implementation. I was hoping that someone > could say something > > > like, "oh yeah, JBoss does 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. > > > > Ok, I'll make a more helpful effort than "fix JVM". > > > > When the JVM crashes, does it dump stacktraces for the running > > threads? I've > > seen many JVMs do this, and it might give you a clue as to > what's going on > > at the time. > > > > You could also try taking thread dumps (kill -3) up until > the time when it > > crashes. > > > > Toby. > > > > ___ > > 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 > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] What happens at 6 hours and 35 minutes?
Thanks, Toby. There's no backtrace on the threads, just the typical "Memory fault: core dumped" message. I will try the kill -SIGQUIT, and see if that gives any insight. The java profiling 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 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 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 a > > JVM problem with SCO's implementation, but unfortunately, > there's nothing I > > can do about that, SCO being such an awesome > > implementation. I was hoping that someone could say something > > like, "oh yeah, JBoss does 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. > > Ok, I'll make a more helpful effort than "fix JVM". > > When the JVM crashes, does it dump stacktraces for the running > threads? I've > seen many JVMs do this, and it might give you a clue as to what's going on > at the time. > > You could also try taking thread dumps (kill -3) up until the time when it > crashes. > > Toby. > > ___ > 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
Re: [JBoss-user] What happens at 6 hours and 35 minutes?
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 a > JVM problem with SCO's implementation, but unfortunately, there's nothing I > can do about that, SCO being such an awesome > implementation. I was hoping that someone could say something > like, "oh yeah, JBoss does 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. Ok, I'll make a more helpful effort than "fix JVM". When the JVM crashes, does it dump stacktraces for the running threads? I've seen many JVMs do this, and it might give you a clue as to what's going on at the time. You could also try taking thread dumps (kill -3) up until the time when it crashes. Toby. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] What happens at 6 hours and 35 minutes?
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, SCO being such an awesome implementation. I was hoping that someone could say something like, "oh yeah, JBoss does 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
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
Re: [JBoss-user] What happens at 6 hours and 35 minutes?
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 > looking at the source code, but I've been unable to find a correlation that > might lead me to find what's happening. I am using the latest jboss/tomcat > binary distribution launched with run_with_tomcat.sh. > > Anybody have any ideas? Use a less buggy JVM? I think this would be better taken up with the JVM vendor. Toby. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
