Author: Vernon Broussard
We're running ColdFusion 7.02 on a Windows 2003 production server(IIS 6) that
appears to have a memory leak or coding issues or both. The jrun.exe will run up
to 1.2 gig of usage and higher in task manager. Somewhere above 900mg of usage
the CF processes will lock up causing us to have to stop jrun and let it restart
or in some cases, reboot the server. Obviously, this plays havoc with our CF
applications and pages. In addition, we have also located what appears to be
coding errors in the CF application logs. some examples are, 'dividing by zero',
'items undefined', 'access page timers being exceeded'. As we are not CF
programmers on our side of the issue we don't always know what effect these
errors have on the processes on the server. The logs have been forwarded to our
application support/programming section and it appears some corrections have been
made and are continuing to be made. On Monday,7/18, we were required to restart
jrun approx 14 times throughout the day and evening on this server. This slowed
through the rest of the week up to this point with some specific times when it
had to be restarted at approx 3-4 hundred meg, instead of 900mg to 1.2 gig.
Update: many coding errors have been repaired over the last week and the high
number of restarts has dropped but still present. On the ColdFusion side we have
applied a hotfix 65335 which is suggested to work with the way jrun releases
memory with file uploads. This didn't appear to make any difference when applied
but we suspect there is a problem with the path it was applied to. We are
correcting that today.
I have also looked at one of the CF updater files to try but in the past applying
one of these may have fixed one error but created others.
We are looking at the JVM version because I have seen in some of the blogs where
there are a couple of less beneficial versions and an upgrade can help. we're at
1.4.2_09 but I've read where _13 or _19 would be better.
We are in the process of testing applications in the CF 8.0 region that is setup
(and making it a priority)but this won't happen overnight. May take several
Please, anyone who has seen similar errors with jrun in a 7.02 environment, can
you offer some quick fix solutions, or even not-so-quick?