kennethteo.com

I am observing pretty bad performance when my BlazeDS services are configured with Apache and Tomcat on mod_jk. Not too sure whether it is because i used Cairngorm as my main application framework. Setting requestTimeouts on my remoteObjects didn’t help. It was until i tried hitting my BlazeDS endpoint directly with my browser that i realised it was Apache that had refused/restricted requests to my Tomcat.

Error message from Apache

What i see on the Apache Error log

Tue Jul 22 18:51:59 2008] [error] [client <ip address>] client denied by server configuration: amfsecure, referer: <url to my flex app>

but i do not see any request with the same timestamp on the Tomcat logs.

Performing tuning is the only way to go. However, my sys admin did hardened and tuned the mod_jk connector settings in the server.xml files. Still waiting for him to try to worker.properties file. Sys Administration is not my kind of work. =p

My guess is that unless you are expecting very low traffic, you should not use the mod_jk setup. I hope my sys admin ain’t gonna get hell from me to ask for a public-facing Tomcat. I sent a message onto the BlazeDS jira below to see if there is any advice on my situation.

References:

• http://bugs.adobe.com/jira/browse/BLZ-84
• http://www.solutionhacker.com/2008/05/29/tomcat-performance-tuning/

Some rules to remind myself

1. KISS
   • Reduce the use of nested containers
   • If you use many VBox-es and HBox-es to maintain proper layout, you might be better off with a Canvas
2. Use List, HorizontalList, TileList controls and sometimes repeaters(though List controls are still preferred)
   • Only the controls within the visible area will be generated for the List, HorizontalList and TileList controls.

http://livedocs.adobe.com/flex/3/html/help.html?content=Part2_DevApps_1.html
http://www.adobe.com/devnet/flex/articles/client_perf_04.html

Tags: flex, UI, design