Is there any scenario in which Tomcat 4.0 or 4.1 will kill off processor threads?
I know that under apache, it is possible to limit the number of spare processes, in which case the controller process will kill off extras when load decreases. Alternatively, is there any error condition under which a thread will be considered hung or otherwise corrupted and killed off? Our application maps certain objects on a per-thread basis, and I'm worried that we may end up with memory leaks when objects remain referenced in our map even though the thread they are assigned to is no longer valid. (And yes - I know this is probably a bad design, and we're looking into some refactoring there, but not a week before a release if we can avoid it...) Either there hasn't been any discussion of this topic in the archives or (more likely) I just didn't hit on the right combination of keywords to search on. And I can't convince myself one way or that other from the code. ;) Thanks in advance, Aaron ----------------------------------------------------------------------- Aaron Dunlop Product Development Engineer TransCore Commercial Services, Inc. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
