Skip to main content
Inspiring
June 17, 2014
Question

Web Connector Settings

  • June 17, 2014
  • 3 replies
  • 2497 views

I am reviewing the ColdFusion Web Connector settings in workers.properties to hopefully address a sporadic response time issue.

I've been advised to inspect the output from the metrics.log file (CF Admin > Debugging & Logging > Debug Output Settings > Enable Metric Logging) and use this to inform the adjustments to the settings max_reuse_connections, connection_pool_size and connection_pool_timeout.

My question is: How do I interpret the metrics.log output to help with the choice of setting values? Is there any documentation that can guide me?

Examples from over a 120 hour period:

95% of entries -

"Information","scheduler-2","06/16/14","08:09:04",,"Max threads: 150 Current thread count: 4 Current thread busy: 0 Max processing time: 83425 Request count: 9072 Error count: 72 Bytes received: 1649 Bytes sent: 22768583 Free memory: 124252584 Total memory: 1055326208 Active Sessions: 1396"

Occurred once -

"Information","scheduler-2","06/13/14","14:20:22",,"Max threads: 150 Current thread count: 10 Current thread busy: 5 Max processing time: 2338 Request count: 21 Error count: 4 Bytes received: 155 Bytes sent: 139798 Free memory: 114920208 Total memory: 1053097984 Active Sessions: 6899"

Environment:

- 3 x Windows 2008 R2 (hardware load balanced)

- ColdFusion 10 (update 12)

- Apache 2.2.21

This topic has been closed for replies.

3 replies

Legend
June 17, 2014

Hi Richard,

I used to like metrics logging CF9 and before however since CF10 have not found it overly useful. Note to self go check metric logging in CF11. Well then what can you do to know what is going on? Use other tools.

I generally think performance gains can be found by making connector adjustments in CF10 and CF11. There was a recent blog entry that relates and tho covering CF11 / IIS in topic I think subject matter also applies to CF10 and Apache.


http://blogs.coldfusion.com/post.cfm/coldfusion-11-iis-connector-tuning

Keep in mind my daily environment is Windows IIS where as you use Apache. I have a done a small amount of testing on Apache and think worker.properties and server.xml changes are similarly important.

I discussed my thoughts on connector adjustments here and also demonstrate use of tools to know what is going on.

http://experts.adobeconnect.com/p8l51p4s9m4/


HTH, Carl M.

Inspiring
June 18, 2014

@Carl M - If you see the last half dozen comments on that ColdFusion blog you'll see me having a "conversation" with Anit Kumar Panda of Adobe. Anit has been very supportive and has offered to call me to discuss my issue. I'll feedback the results here.

I have watched your Connect session several times. Most helpful, thanks. It gave me the insight, via JConsole, to see the results of changes to connection_pool_size / maxConnections and connection_pool_timeout / keepAliveTimeout. I'm guessing that I won't see any entry in JConsole for max_reuse_connections as my understanding is that this setting is part of Adobe's customisation of mod_jk?

My issues still stands. I now have lots of information (metrics.log and JConsole output) but no knowledge of how to use it to inform worker.properties / server.xml settings.

I'll capture a day's worth of currentThreadCount / currentThreadBusy chart data and post it back here with my worker.properties / server.xml settings later today to aid the debate.

Inspiring
June 18, 2014

As promised, here are some screen grabs from a good period of activity...


The worker.properties and server.xml files for the instance are unchanged from the default install (max_reuse_connections=250 only).

My interpretation of this is that thread count reached a maximum of around 50 which is well within the maximum allowed of 200.

The result I can't explain is that the thread busy count seems to be dropping as soon as the thread is no longer in use. The Tomcat Connector docs (http://tomcat.apache.org/connectors-doc/reference/workers.html) state that the default value is indefinite (zero). I've not added a value for connection_pool_timeout so I'm guess the Adobe mod_jk is adding the -1 for keepAliveTimeout which I'm also guessing mean "drop as soon as unused"?

I hope this helps inform someone who might be able to make some sense out of all this! :-)

Richard

Carl Von Stetten
Legend
June 17, 2014

No problem.  Maybe just mention the cross-posting next time so people on different forums don't work at cross-purposes.  Good luck!  And by the way, I'm interested in seeing if anyone responds as you've piqued my curiosity.

-Carl V.

Carl Von Stetten
Legend
June 17, 2014

In case others have an interest in the results of this thread but it doesn't get answered here, this question was initially asked yesterday over on Stackoverflow.  Wish I had an answer for you @Richard.

-Carl V.

Inspiring
June 17, 2014

@Carl - Yes, I raised it there first hoping for a response. When I got none I thought I'd spread the coverage by repeating it here :-)

Inspiring
June 18, 2014

@Carl V - Yes, of course you're right, I'm forgetting my net-etiquette :-)

I'll surely feedback here what I find.