I've seen that happen where 1 page causes JRun to eat up memory. The difference is that it wouldn't stop and an error would eventually be thrown.
This was due to really stupid parsing errors like:
<cfset MyVar = "blah"
or
<cfinclude template="blah.cfm"
or
<cflocation url="">
You get the idea.
I never found a way around this (other than fixing the obvious yet stupid coding errors).
Cheers
Bryan Stevenson B.Comm.
VP & Director of E-Commerce Development
Electric Edge Systems Group Inc.
t. 250.920.8830
e. [EMAIL PROTECTED]
----- Original Message -----
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
