Yingxia, Regarding your second question, you might want to check your logs (default-event.log and admin-event.log) for info on what might be bringing down your JRun server. Be sure in your JMC under logging options for your servers that you not only have "metric" as one of the things to be logged, but also "warning". Lee L. Webmaster Lockheed Martin Corporation -----Original Message----- From: Yingxia Wang [mailto:[EMAIL PROTECTED]] Sent: Friday, March 23, 2001 5:49 PM To: JRun-Talk Subject: JRun dies after the number of busy threads reaches 200 Hi: We are using JRun 3.02 with IPlanet 4.1 on a sunOS 5.7 machine. The whole system was up and running fine for a month (except restart the JRun server one or twice a week). But lately we ran into a lot of problems with JRun. It appeared slow in the beginning, and then died. We have logged the metric information, I can see the number of busy threads jump from the normal level (~10) to 200 within a 5-10 minutes. It's just hanging after that, and nothing get process further. I wondered if anything could cause JRun accumulate thread like this. Will it help if we increase some number associate with thread limit? One thing even more mysterious: Several times, when the JRun went down, every time we restart it, it went down within 10 minutes. It's acting like that for hours, and then, all of sudden, without changing anything in the system, it became stable again and stayed that way at least for a day or two. Any idea of what could cause that? Any help would be appreciated, Thanks. Yingxia ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
