Sadly there is no mention of a fix related to NIO in the 6u12 release notes. This comes as kind of a bummer, as we were hoping to make a comet implementation soon.
The native/apr connector looks like it could be a replacement for NIO for us, but after searching I could not find anything conclusive about the scalability and performance compared to NIO. Opinions on native vs nio in discussions I have found seem to be divided. I'm also not sure if the native/apr implementation is completely separate from the NIO api. Does anyone know of any downsides/pitfalls I should look out for when using native/apr ? As always, any comment is appreciated. - Taylan -----Original Message----- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: dinsdag 17 februari 2009 16:36 To: Tomcat Users List Subject: RE: Fatal error: Cleaner terminated abnormally > From: Taylan Develioglu [mailto:tdevelio...@ebuddy.com] > Subject: Fatal error: Cleaner terminated abnormally > > Lately we've been experiencing a fatal error, related to gc, > with Tomcat that causes it to stop and unload It's not really a GC problem - rather a silly bug in NIO. You might try the standard HTTP connector to avoid the problem. Sun seems to be continually fixing NIO, so there may be something for this in 6u12, if you want to keep using the NIO connector. > I'm still unclear on what is causing the cleaner to terminate The Cleaner terminates if the run() method of the registered object throws *any* kind of exception - and then takes the entire JVM down with it, via a System.exit() call (bloody brilliant, that one). In this case, the NIO Selector Closer object didn't like the fact that its peer had gone away, and puked. Not quite as robust as one might hope. - Chuck --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
