I'll be sure to post an update if u16 resolves it. Or any other progress for that matter.
In the meantime don't be shy either :) On Wed, 2010-02-24 at 14:52 +0100, Carl wrote: > Taylan, > > > The failures we've seen are in anywhere between 8 hours to a week of > > runtime. > > The timing of the failures seems similar. > > > We have also had failures with hotspot error files (hs_err) present, and > > the cause specified was indeed SIGSEGV indicating a page fault. > > I have never seen any hs_* files but have seen core files where strace > showed the jvm stopped on a seg fault. > > > We also use jdk 1.6.0_18, I'm downgrading the machines to 1.6.0_16 when > > the situation allows (during regular updates of the application, or a > > crash) to see if that helps. > > I have used jdk 1.6.0_17 and 1.6.0_18 with the same results... have not > tried 1.6.0_16. Please post your results of this trial. > > > Running tomcat on the > > foreground might show something, but then again I could be waiting for a > > month for it to happen. > > Yes, this has been part of my problem as anytime we change something, we > have to wait a week for the server to fail. > > In one sense, I am fortunate that I have a little more flexibility than you. > I have two servers (different hardware) but only need one in service at a > time. Therefore, I always have one server I can test ideas on although I > have never been able to develop a meaningful stress test, i.e., the only way > I can test a change is to put it in production. > > Thanks, > > Carl --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
