Ming Lu, If you find jrun running out of memory you have several options. A) Increase the maximum memory B) determine what is using so much memory and try to minimize it C) check if you have a memory leak and try to fix it
The easiest is option A). You just have to edit your jvm.config file in the bin directory in your jrun install. And change the -Xmx setting. For B), you mention you have a log of session variables which could also be application variables. The application scope is a shared scope, which means all your sessions could share the same variable. This would cut down on your memory usage in a big way, but only if the variables are the same for all users. A Session.userID would not work as Application.userID because it is unique for each session. Leon -----Original Message----- From: Ming Lu [mailto:[EMAIL PROTECTED] Sent: Monday, March 06, 2006 9:39 AM To: CF-Talk Subject: JRun High Memory Usage on CFMX 7 Hi, Our sites running on Windows Server 2003 with CFMX 7 use session variables (Maximum Timeout has been setup as 40 minutes). Recently we noticed that the high memory usage for JRun is always associated with high numbers of openned sessions. Metrics logging showed that sometimes sessions reached more than 40 and at the same time the JRun used about 400 MB memory, which caused the JRun to a halt and the sites couldn't be displayed. It happens almost once a day recently. Does anyone know a solution to this problem? Should we replace all the session variables with application variables? If so what is the best Maximum Timeout for application variables? Thank you very much in advance! Ming Lu ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:234430 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
