Well, we're are not using Client Variables at all.  So we have to look for
another cause.

Kind Regards,
Dave Hannum
===============================
David R. Hannum
Web Analyst/Programmer
Ohio University Computer Services
(740) 597-2524


----- Original Message ----- 
From: "Robert Walters" <[EMAIL PROTECTED]>
To: "CF-Server" <[email protected]>
Sent: Wednesday, July 20, 2005 4:38 PM
Subject: Re: CFMX 6.1 Jrun CPU/RAM spasm


> I am just going through this with 7.1
>
> In your admin check to see where you are storing client variables and
> how often it purges them.  I found mine was storing them in the registry
> and was purging them every hour.  Thus every hour I would get 99% Jrun
>
> Sometimes it would freeze the server.
>
> Thanks....Rob
>
> Dave Hannum wrote:
>
> >We're running CFMX 6.1 on JRun 4 on Windows 2003 & IIS 6.0.  We're
running
> >the CommonSpot CMS on this machine.  Normally the CPU behaves normally
and
> >the RAM runs between 1.05 & 1.25 GB.  Each day, usually between Noon and
> >3pm, the CPU spikes to 100% (97%+ JRun) and the system slows way down.
> >After about 5 minutes of this, the RAM dives off the end of the table to
> >about 450MB or so.  The CPU settles down, and the RAM starts building
back
> >up (caching pages from the CMS).  Does anyone have any clue what's going
on
> >with JRun when this spasm occurs?
> >
> >Kind Regards,
> >Dave Hannum
> >===============================
> >David R. Hannum
> >Web Analyst/Programmer
> >Ohio University Computer Services
> >(740) 597-2524
> >
> >
> >
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Stay Ahead of Hackers - Download ZoneAlarm Pro
http://www.houseoffusion.com/banners/view.cfm?bannerid=65

Message: http://www.houseoffusion.com/lists.cfm/link=i:10:5501
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/10
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.10
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to