JRUN runs off the chart!

[QuietObserver]

I'm sorry to open up old wounds; however there doesn't seem to be a definitive
solution to this one. We are running several different sites running on CF MX
7.0.2.142559 on Win2k3 box (patched). JRUN memory usage pegs on us several
times a day, forcing us to restart the Coldfusion service. We have automated
this process to reboot when JRUN has used up 900 mb of memory.
I got a good laugh today when an ADOBE support rep told me that all CF support
was fee based. Starting at $499 per incident. : - O I got a good chuckle out
of this, considering that this JRUN issue started after our Server was upgraded
from CF 6.1 to 7. You?d think that this ?BUG? as I would call it, considering
the hundreds of posts out there about it, would make Adobe consider looking
into the issue and coming up with a ?hot fix? for it. Anyways, enough of my
ranting? I am trying to resolve this issue and not wanting to pay for the
support, I am posting it here as I was directed by the CF Support Rep?

Here are my Web Server specs.
Windows 2003 Web Edition (patched and updated)
2.8 GHz Dual Xeon Processors
2 GB RAM
CF MX 7.0.2.142559
Java Version 1.4.2_13
Min JVM Heap Size 1024
Max JVM Heap Size 1024
JVM Arguments:
-server -Dsun.io.useCanonCaches=false -XX:MaxPermSize=128m
-Dcoldfusion.rootDir={application.home}/../
-Dcoldfusion.libPath={application.home}/../lib -XX:+PrintGCDetails
-XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,address=2899 9,suspend=n

Debug is off
Whitespace management is also turned off.

All data sources are querying an MSSQL 2000 database?

Most other settings are default to the install.

I?m not a CF expert and these are settings that were on our production server
before I joined the company. I don?t have a clue as to where to start. I have
read most of the post on this forum about this issue, however as I pointed out,
there is no definitive solution to the problem. Any help is greatly
appreciated.

[ke4pym]

There is one thing that will cause CF to start sucking up a lot of memory -
your code. Did anyone check it to make sure it was compatible with CF7?

Also, these lines:

-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,address=2899 9,suspend=n

turn on monitoring of your JVM. They can be expensive to have on if you're
not actively monitoring your server.

Your other JVM settings look fine, though I've never been a proponent of
static JVM sizes.

Look at paying for support this way - would you rather pay $499 for them to
start helping you, or would you rather pour countless hours into your problem
at an untold cost?

Posting some logs from around the time of your crashes might be helpful for us
to get started on what is going on.

Also, what are your max thread set for?
What are your max cached queries set for?
Do you maintain connections to your DB server?
Do you limit the number of connections to your db server?
Do you have a time out set?
Have you updated the JDBC drivers?

[QuietObserver]

Maximum number of simultaneous requests: 30
Maximum number of report threads: 8
Maximum number of cached templates: 1024
Maximum size of post data: 500 MB
Timeout Requests after (seconds): 18000
Have you updated the JDBC drivers? Drivers are updated as per this article
(version 3.5)
[url]http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=42dcb10a[/url]

The number of connections to our db is not set.
I?m not sure if the db connections are maintained??? Can you give an example
of how this would be done in code?
As for our code, our web team has examined much of the code and informs me
that it all ?should be? compatible. Is there a reference I could check
against?

Do you have a recommended JVM statement?
What error logs would I look at the get examples from, so far it has crashed 3
times today...

[ke4pym]

Pull your simul. req. down to no more than 6-7 per physical processor.

Is there any reason you're allowing threads to run for 5 hours? You really
shouldn't allow your timeout requests go much longer than 60 seconds. If
threads run longer than that and they hang you'll crash CF. If code needs
longer than 60 seconds, your devs should specifiy it in their code (but not 5
hours).

Check your db connection/maintaining in the CF Admin in the datasource itself
under advanced options. You should set the max number of connections to 6-7
per CPU as well.

As for logs, check your application and server.log files. Plus, look in your
JRun logs folder for other logs. cfusion-out.log and cfusion-err.log are good
places to start.

What version is ColdFusion? Standard or Enterprise? How do you have it
installed? Stand alone? Or is it J2EE (only if you have Enterprise).

[QuietObserver]

It is the standard version. I will look into the things you posted here. I do appreciate your input!