Kernel Panic happens due to bug at the kernel level. Normally, even deeply broken applications should not generate a kernel panic. Possible causes: 1) Broken network module, which generates an error during unbinding of tomcat from interface. Unless your interface model is very recent and kernel module associated with it is indicated 'experimental', should not happen 2) Broken hardware. A broken network interface could generate unexpected irq, return values in unexpected range to driver, which could then crash if such condition was not expected. Also, i'll recommend to check the most common cause of kernel or random application crash : memory. Run a memtest86 for a few hours to ensure memory is not broken.
My bet is on network interface, if this happens systematically. Try unloading network interfaces then start/stop tomcat, it will only attach to localhost, where no network hardware is involved. En l'instant précis du 09/05/07 13:41, Rogerio Pazini s'exprimait en ces termes: > Hi, > > I´m just trying to configure a new server with RHEL 4.0 installed > together > with JDK 1.6.0 and Apache Tomcat/5.5.17 installed. We have no problem to > start it up (Tomcat) but when it try to shut it down, I have many kernel > panic messages and the machine got frozen. Does anybody had similar > problem > before ? If positive what could be happening ? > > Tks in advance ! > > Rogério > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
