The current settings for our JVM ({drive}\Jrun\bin\jvm.config) is this:
# Arguments to VM
java.args=-server -Xmx1024m -Xms1024m -Dsun.io.useCanonCaches=false -Xbootclasspath/a:"{application.home}/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/webchartsJava2D.jar" -XX:MaxPermSize=128m -XX:+UseParallelGC -XX:+UseAdaptiveSizePolicy -DJINTEGRA_NATIVE_MODE -DJINTEGRA_PREFETCH_ENUMS
If I recall, the default settings for Jrun don't have UseAdapativeSizePolicy nor a min heap stack (-Xms), the first of which is listed as 'required' when you have UseParallelGC, here: http://wireless.java.sun.com/midp/articles/garbagecollection2/. the second of which was mentioned as preferred by MM: http://www.macromedia.com/support/coldfusion/ts/documents/cfmx_perf_tips.htm.
You'll also find an article here on performance and tuning for Jrun: http://www.macromedia.com/devnet/java/articles/jrun_perf.html, Keep in mind that it mentions 'latest' OS and and JVM tips and tricks, but there's no date or version reference that I noticed so I have no idea what 'latest' means.
But we didn't reach 'relative' stability until we discovered the next gem that the JDBC drivers provided with the install were presenting problems:
We also downloaded the replacement JDBC drivers listed on the MM the tech article here: http://www.macromedia.com/support/coldfusion/ts/documents/cfmx61_sqlserver_cpu.htm.
But we still aren't stable as we are still having unresolved issues such as:
The problem described here: http://webforums.macromedia.com/coldfusion/messageview.cfm?catid=6&threadid=684306&highlight_key=y&keyword1=No%20more%20data%20available%20to%20read%2E, which is caused by replacing the drivers in the previous step and is two JDBC driver sets backwards. We've been testing in Development, and will be rolling forward soon.
We're also peridically getting this error: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]There is insufficient system memory to run this query. "
All in all, I'm pretty disatisfied with the current scenario as far as CFMX on Jrun is concerned, it still doesn't feel stable or deployable beyond our test case, and we are using ColdFusion 5 based code for this (adjusted to compensate for MX differences).
- Calvin
----- Original Message -----
From: Kurt Wiersma
To: CF-Talk
Sent: Friday, October 10, 2003 8:42 PM
Subject: JRun java.lang.RuntimeException
We are running CF MX 6.1 Enterprise under a full verson of JRun. After about
6 hours the Jrun stops processing requests and throws the following
exception in the logs. This exception appears many times in the log prior to
the server becoming unresponsive. Restarting the CF Jrun server instance
fixes it. Has anyone else seen this error?
java.lang.RuntimeException: Request timed out waiting for an available
thread to run. You may want to consider increasing the number of active
threads in the thread pool.
at jrunx.scheduler.ThreadPool$Throttle.enter(ThreadPool.java:125)
at
jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:448
)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
--Kurt
Web Applications Developer
American Academy of Neurology
www.aan.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
