The engine class only does some initialization, we did not implement it all :-) Thanks
Caldarale, Charles R wrote: > >> From: Michal Singer [mailto:[email protected]] >> Subject: RE: Accumulation of Request Processors objects causes tomcat >> stuck? >> >> Uploaded server.xml > > Your <Executor> elements have no attributes other than names, so you're > using the defaults. To quote from the doc: > "minSpareThreads (int) The minimum number of threads always kept alive, > default is 25" > > Since you have three <Executor>s, you'll see at least 75 threads hanging > around all the time (once they've been created). The RequestProcessor > items you see in the MBeans tab are just information about the last > request each thread handled. > > Again, if you think Tomcat is stalled, take several thread dumps; browsing > the MBeans isn't going to help. > >> <Engine className="com.expand.expandview.tomcat.ExpandViewStandardEngine" >> defaultHost="localhost" name="Catalina"> > > Using your own Engine class? Gutsy... > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete the e-mail > and its attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://old.nabble.com/Accumulation-of-Request-Processors-objects-causes-tomcat-stuck--tp26791905p26823241.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
