What is the approved Java version for JRun4 with CF9.01

[Joop Kaashoek]

We use CF9.01 on 64bit Linux with JRun4 and Apache, with the included JRE 1.6.17 or so. I have not found Adobe's published list of approved Java versions for each platform, but can we upgrade to a Java 7 SDK for instance?

Given that we are also experiencing 'Server Busy, Too many concurrent requests' error that we have trouble eradicating, would getting rid of JRun and moving to TomCat  be a wise thing to do?

[carl type3 · Accepted solution]

Adobe officially support CF8 & CF9 with Java dev kit 1.6.0_24:

http://blogs.adobe.com/coldfusion/2011/03/15/jdk-1-6-0_24-is-now-officially-supported/

and this reference:

http://kb2.adobe.com/cps/894/cpsid_89440.html

In some cases I have used in development Java dev kit 1.7.0_01 on Windows.

I gather CF10 / Zeus is going to be tomcat versa java based.

HTH, Carl.

[Dave Watts]

We use CF9.01 on 64bit Linux with JRun4 and Apache, with the included JRE 1.6.17 or so. I have not found Adobe's published list of approved Java versions for each platform, but can we upgrade to a Java 7 SDK for instance?

While some functionality might work with Java 7, I strongly suspect that many features will not work. I wouldn't recommend this for production use.

Given that we are also experiencing 'Server Busy, Too many concurrent requests' error that we have trouble eradicating, would getting rid of JRun and moving to TomCat  be a wise thing to do?

Why do you think that would make a difference?

Dave Watts, CTO, Fig Leaf Software

[Joop Kaashoek]

I am thinking that would make a difference since the error is a JRun-specific error, hopefully TomCat has implemenented better request handling. But it is not a certainty of course.

[Dave Watts]

While the error message itself is specific to JRun, it is not the case that you can't have more requests than you can handle on ... anything else, including Tomcat. Chances are very high that you would simply encounter the same problem, with a different error message, if you migrated your current application to Tomcat and nothing else was changed.

Dave Watts, CTO, Fig Leaf Software

[Joop Kaashoek]

We have enabled logging and nothing indicates that we are running out of threads at the time we get the error. Our thread config is as follows, in the instrance's JRUN.XML file

  <service class="jrun.servlet.jrpp.JRunProxyService" name="ProxyService">

    <attribute name="activeHandlerThreads">10</attribute>

    <attribute name="backlog">500</attribute>

    <attribute name="deactivated">false</attribute>

    <attribute name="interface">*</attribute>

    <attribute name="maxHandlerThreads">390</attribute>

    <attribute name="minHandlerThreads">5</attribute>

    <attribute name="port">51003</attribute>

    <attribute name="threadWaitTimeout">300</attribute>

    <attribute name="timeout">300</attribute>

When the error happens, our metrics reporting shows th following:

ikm_online-metrics.log:01/16 11:05:12 metrics Web threads (busy/total): 0/25 Sessions: 416 Total Memory=1046592 Free=597788

So yes, the nr of requests (presumably 25, the nr of threads, not 100% sure)  is higher than the activeHandlerThreads value, but not as high as the maxHandlerThreads value.

That is the puzzling part...

Is there any other set of configuration parameters to tweak as well?

Thanks for your help!

[Joop Kaashoek]

Checking any thread/process limits on Linux..

[Joop Kaashoek]

Created a new discussion for this topic.