Makarand, I have seen similar behavior. I think there may be a JRun problem. If I setup a threadpool of 50 with an idle thread timeout of 60, then after a fresh jrun startup and no activity NT perfmon shows the threadpool gets cleaned up. Or if I send a burst of 100 persistent connections, then after 60s the threadcount goes from 150 to 100.
I am going to try an experiment with the IBM jvm later this week to make sure this isn't VM related. I've had best performance leaving the threadpool at 1, even thought that's not what's desired, my server/VM lives much longer that way. I'm assuming that changing the threadpool causes a fault inside JRun. Anyone know more? BenG. JOGALEKAR,MAKARAND (HP-Boise,ex1) wrote: >Hello, > >We are having lot of problems with JRun 3.0 or Jrun3.1, >If we get high volume and the thread count goes beyond 100, it does not >respond. > >We are just using servlets with Netscape Exterprise server 3.6 with EJB's at >all. > >We have disabled the EJB option for performance and also tried different >options >by setting initial thread count to 50 with maximum thread count to 500..but >nothing works.. > >Any help ?? > >Thanks, >-Makarand > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
