Roar, unless you make special provisions each servlet request would be another thread. Could it be that your threads (requests) are not exiting but blocking on some resource? Can you throttle demand for that resource by including a synchronized method wrapped around that resource? Just a thought. BenG.
Johansen, Roar wrote: >Ben Groeneveld wrote: > >>Makarand, are you hitting JRun thru the Netscape Webserver? Then your >>problem may be with its max concurrency setting. I have seen this with >>IIS as the front-end to JRun. How many concurrent connections will your >>Netscape Webserver accept? Make sure you are updating the external web >>server settings and not the JRun web server. Hope that helps, BenG. >> > >--------- > >Does anybody have any thoughts as to why the number of threads even rises to >100? We are running a site that serves over 1200 pages a minute in peak >hour, distributed among 6 unix servers. This means that any one server >continuously serves 3-4 pages a second and does so with a minimum effort. In >fact, any server rarely has more than 20-30 threads active at any time (we >measure this by 'netstat -n | grep ESTABLISHED | grep <JRun connector port >number>'). However, from time to time this figure rises dramatically during >a few seconds, often ending at the 100 threads, where it eventually locks >up. My feeling is, you can bump the limits in JRun, NS and unix, but when >this rise occurs, it will eventually eat up any resources you feed it. I >personally am very interested in finding a reason for this sudden rise. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/jrun-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
