here's the first update on that: ibm's jvm doesn't work either... to make it clear: I do not say that this *MUST* be a tomcat-bug, but I would appreciate sharing any experience with that and I would be thankful for *any* suggestion (besides writing a script that restarts tomcat :-) pero > -----Original Message----- > From: pero [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 20, 2001 8:55 PM > To: [EMAIL PROTECTED] > Subject: tomcat 4 (final) quits without notice > > > Hi there, > > After months of developing with tomcat 4 (yes, I was there from the very > first beta :-) I always considered tomcat to run in the production > environment, too. > While it is working fine on my staging-server (Suse Linux 7.2, Sun's 1.3.1 > JDK) it stops after a random amount of time on my production server, which > is also Suse Linux 7.2. > According to the last discussions on the mailinglists I started using > different VMs (Sun's 1.3.0, 1.3.1 and 1.4.0 Beta 2) but the result was the > same. Now I'm on my last try with IBM's 1.3-9.0 (which I did not intend to > use...) > If that doesn't work either - I got a very serious problem, because the > project I am working on is going to go final very soon. > > In another project (my band's homepage) I use tomcat 3.1 since january and > all works fine... It works under Suse 6.2 and Sun's 1.3.0. > > Are there others facing the "die"-problem? > > pero > >
