JRun Memory Leak

[Augusoft]

Since upgrade to ColdFusion MX7 Enterprise the memory consumption of JRUN.EXE
gradually climbs (pace of consumption depends on load) until all web sites
stall. Even the CF administrator app stalls. Relief only comes by restarting
the CF Application service. Even a restart of the service times out. Within
minutes, the service is startable again and the cycle repeats.

[xentrix]

Any info in your logs, both the CFAdmin ones and the JRun logs?

Andy

[TylerWebGeek]

I'm having the same problem with CFMX 6.1. If I kill the jrun.exe process it
will restart itself and everything will run fine...for a while. This is getting
pretty frustrating. The JRun logs have the following entry multiple times:

java.lang.OutOfMemoryError

Any ideas for solutions?

[Augusoft]

The main contributor to our problem, as we later identified, was poor code
(bad programming). The solution was to signficantly limit the number of
session variables per page/template as well as refining RAM and CPU hungry
queries. We identified that having a large number of session variables
accompanied with improper use of CFLoop and no use of CFParam caused JRUN to
keep grabbing memory while not releasing memory when the session/variable
expired. For us, this only occurred when using a database for client
variables. Our SQL logs showed numerous process lock problems related to
JRUN's inability to release the memory. Even tuning ColdFusion (i.e. garbage
collection, template caching, query caching, etc.) did not resolve the problem.
Fixing enough bad code did.