maximum number of JRun threads on CF8 Standard

[Passthedutchie]

Hi,

I have been looking to increase the maximum number of JRun threads on
CF8 Standard on Linux. However, changing jrun.xml (<attribute
name="activeHandlerThreads">100</attribute> in the JRunProxyService
section) did nothing after restarting CF and Apache and I have not
been able to find it anywhere in the Administrator. Anybody have any
ideas or have I missed something really obvious?

CF administrator does not list the value anywhere apart from the
settings summary.

Thanks

Meint

[charlie arehart]

Meint, I'm pretty sure that in CF Standard, the "max number of simultaneous
template requests" setting (in the CF Admin) correlates directly to that
activehandlerthreads setting in the jrun.xml. You should find them remaining
in sync as you change them (though changing the xml file would require a
restart of CF to pick that up). You said that changing it "did nothing"
after a restart. Can you elaborate?

/charlie

[Passthedutchie]

Hi Charlie,

I changed the setting as described above and restarted both Apache and
CF Server. however, when I looked at the "Settings Summary" link
inside the CF Administrator after restarting, it still said:

Simultaneous request limit 100
CFThread Pool Size 10
Maximum number of report threads 1
Maximum number of running JRun threads 100
Maximum number of queued JRun threads 1000

This leads me to believe that the change made wasn't picked up or did
the administrator simply not reflect the current value? Do you know if
there a different way of finding the current value so I could double
check? Platform is CF8 standard on RHEL 5. Am I correct in thinking
there is no point in turning up the CF "Maximum number of simultaneous
Template requests" without changing the JRun settings as the CF
requests would simply end up being queued by JRun anyway?

Regards
Meint

[Passthedutchie]

Sorted, turned out I changed the wrong parameter, it should have been
this one:

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

Comments inside the file led me to believe that was for the internal
web server only, but it appears to even be the one with Apache.
Everything now works as expected in development, still interested in
finding out a bit more in my question above though, i.e. am I correct

[charlie arehart]

Meint, I'm not understanding. If you changed the limit to 100 in the CF
Admin, that's reflected in the report below, both in terms of the CF
(Simultaneous request limit ) and JRun (Maximum number of running JRun
threads ) settings. Are you meaning something I'm not seeing?

/charlie

> -----Original Message-----
> From: fusion...@googlegroups.com
> [mailto:fusion...@googlegroups.com] On Behalf Of Passthedutchie
> Sent: Thursday, October 22, 2009 6:38 AM
> To: FusionReactor
> Subject: FusionReactor Group: Re: maximum number of JRun threads on CF8
> Standard
>
>

[charlie arehart]

But Meint, you had said that WAS the one you were changing in your original
note:

"However, changing jrun.xml (<attribute
name="activeHandlerThreads">100</attribute> in the JRunProxyService
section) did nothing"

I'm pressing this for reasons having to do with your final question here,
also.

As for your original note, I had noticed that you had said you were changing
the activehandlerthreads setting in that JRunProxyService section. Had you
instead said you were doing it in the <service
class="jrun.servlet.http.WebService" name="WebService"> section, I would
have pointed out that potential confusion, which is easy.

So to be clear, it's the latter that has to do with the internal web server
processing and the former which (as you note) has to do with external web
servers (IIS, Apache, etc.)

Anyway, glad you got it sorted.

As for your final question, again the point is that there should be no
difference between the CF and JRun settings. Changing one should change the
other. They shouldn't get out of synch. Are you not seeing that (again,
changing it in JRun would require a restart of CF for it to be picked up, or
perhaps there's also an Admin API call that could force it, but I doubt it.)

/charlie

> -----Original Message-----
> From: fusion...@googlegroups.com
> [mailto:fusion...@googlegroups.com] On Behalf Of Passthedutchie
> Sent: Thursday, October 22, 2009 1:46 PM
> To: FusionReactor
> Subject: FusionReactor Group: Re: maximum number of JRun threads on CF8
> Standard
>
>

[Passthedutchie]

Hi Charlie,

Apologies, I created that confusion by quoting the wrong one in the
follow up post, so will try to clarify now.

We run Apache so I originally changed the JRunProxyService thinking
that was the right correct one. However, when checking in CF Admin the
setting had not changed after restarting. After that I posted my
original question here looking for help. It was subsequently pointed
out to me (by somebody on the Adobe forums) that I should have changed
the WebService section in the file. I did this and subsequently did
see the new setting inside CF Administrator. However, my understanding
was the same as I believe yours to be, i.e. it should have been
JRunProxyService for Apache and WebService for the internal webserver
(which we don't use). So, in short I am now a bit confused but have
got it working. Or at least I think it is working because CF Admin
says so? Perhaps CF Admin only ever displays the value for the
internal webserver, regardless of which one you use?

I understand the need to keep JRun and CF settings in sync completely
now, thanks for the clarification. Learnt lots about CF/JVM tuning
over the last few days and seeing very encouraging results in
performance of our application, so many thanks for the assistance.

Regards
Meint

[charlie arehart]

Wow, that would be very interesting to hear, and perhaps could be a bug.
Have you pressed that point on the Adobe forum? I would be interested to
hear their thoughts, especially if you've been fortunate to get an Adobe
person involved in the thread. I wonder, too, if it may matter both the
specific OS and version of CF. Do keep us posted if you learn more. Thanks.

/charlie

> -----Original Message-----
> From: fusion...@googlegroups.com
> [mailto:fusion...@googlegroups.com] On Behalf Of Passthedutchie
> Sent: Thursday, October 22, 2009 7:05 PM
> To: FusionReactor
> Subject: FusionReactor Group: Re: maximum number of JRun threads on CF8
> Standard
>
>

[Passthedutchie]

Okay, good to know I am not going mad after all. I have asked the
question (Administrator section of Adobe CF Forums), I will post if I
get an update. In the meantime our CF Server is flying along, next
week we are going to examine our SQL a bit more to see if we can
squeeze even a bit more performance out. FR rocks!

Regards
Meint

[charlie arehart]

As for analyzing your SQL, since you only just joined up here, I want to
point out something I mentioned last week if you may have missed it: you can
get a LOT of mileage out of analyzing the FusionReactor log files,
especially the JDBC log files. You can find out more at
http://groups.google.com/group/fusionreactor/web/log-parser-commands-for-fr-
3, including info about a free tool, a link to an earlier message with still
more details, and some scripts that I and others have posted to help do such
analysis.

Hope that's helpful.

/charlie

PS BTW, I don't know if it's your intent in using Passthedutchie as your
google name, but I can't help finding every time I respond to you that the
blasted song of that name from the early 80's goes spinning through my head.
:-)

Yep, and that spinning "spins me right round baby, right, round like a
record baby, right round round-round". How do I get off this carousel! :-)
Have a good weekend, all.

> -----Original Message-----
> From: fusion...@googlegroups.com
> [mailto:fusion...@googlegroups.com] On Behalf Of Passthedutchie
> Sent: Friday, October 23, 2009 3:16 PM
> To: FusionReactor
> Subject: FusionReactor Group: Re: maximum number of JRun threads on CF8
> Standard
>
>