Re: [flexcoders] Gotchas with mod-proxy/mod_jk & Flex (Re: Linux Macromedia Flex on Tomcat HOWTO)

[Cary Newfeldt]

you might want to try mod_jk2 if your using apache2. I have that working with an installation of flex on a freebsd box. freebsd install - your mileage may vary -- Yeah I know, not Linux, sorry :) Install mod_jk2 # cd /usr/ports/www/mod_jk2 # make install clean Configured Mod_jk2 Uncommented the following to the httpd.conf file for apache2 to load mod_jk2. # LoadModule jk2_module libexec/apache2/mod_jk2.so Added the following to the httpd.conf file for apache2 to access the workers2.properties file. <IfModule mod_jk2.c> JkSet config:file /usr/local/etc/apache2/workers2.properties </IfModule> Created the workers2.properties file /usr/local/etc/apache2/workers2.properties [logger] level=DEBUG [config:] file=${serverRoot}/etc/apache2/workers2.properties debug=0 debugEnv=0 [shm:] info=Scoreboard. Required for reconfiguration and status with multiprocess servers file=/var/log/jk2.shm size=1000000 debug=0 disabled=0 [lb:lb] [channel.socket:yourServerAddress:8009] port=8009 host=yourServerAddress [ajp13:yourServerAddress:8009] channel=channel.socket:yourServerAddress:8009 group=lb [uri:/jsp-examples/*] group=lb Installing Flex [1] Copy flex-15-lin.bin file to server unzip -d flex flex-15-lin.bin [2] copied flex.war.zip to /usr/local/jakarta-tomcat5.0/webapps/flex [3] copied samples.war.zip to /usr/local/jakarta-tomcat5.0/webapps/samples [4] unzipped each in to the folders above. [5] added samples and flex to workers2.properties file. vi /usr/local/etc/apache2/workers2.properties [uri:/flex/*] group=lb [uri:/samples/*] group=lb [6] restarted tomcat server # cd /usr/local/etc/rc.d/ # ./020.jakarta-tomcat50.sh stop # ./020.jakarta-tomcat50.sh start Hope this works; been a while since I last did this. The server works great, but I find that is sometime craps on out me and I have to restart the tomcat server from time to time. This is not recommended for a production server. cheers, Cary. charlespaz1 wrote: Would you be willing to share your mod_jk configuration? Everything I've found has been either out of date or so grossly inaccurate to be useless. I realize that all requests to Tomcat through mod_proxy are indentified as coming from the proxy server, however, for my current development process, that is acceptable. Eventually I'd like to get mod_jk working, but that's a priority issue, and it isn't one right now. --- In flexcoders@yahoogroups.com, "Eric Raymond" <[EMAIL PROTECTED]> wrote: While I strongly recommend the use of Apache as a front end for Tomcat in production, the use of mod_jk and mod_proxy have some interesting implications with respect to Flex. In my experience, Macromedia was not helpful in resolving these issues. IMHO, mod_jk is much better than mod_proxy. It's a shame the documentation is so obscure ... but I think it is better now than it used to be. If you use mod_proxy, realize that anytime you try to reference the users IP address, you will be getting the address of the proxy server, not the user. By the time the request gets through the flex proxy (not mod_proxy) to your servlet, the orignal info is gone. In many cases you really want to know where your customers are coming from. The way around this is to create a servlet filter that saves the original ip address before the flex proxy so that you can later retrieve it after the flex proxy hands the request to your service. (Confusing eh? There are two proxies here: the apache mod_proxy and the tomcat flex proxy). I believe there were some strange interactions between mod_proxy and ssl. One that comes to mind is that the flex server thinks it is dealing with http so it generates an html mxml wrapper that references things via http. This causes clients to get the "some of the information on this page is insecure" message. Now mod_jk has had problems with the flex proxy. Your mileage may vary: http://www.mail-archive.com/flexcoders@yahoogroups.com/msg05870.html It's been a while but I think there may have been some other issues with HttpSevices (but I'm not sure on this). We've worked around all of them, but we did have to deal with them unexpectedly. Surely others must have run into these roadblocks as well. Perhaps few are using the combination of tools we use: apache, mod_jk, tomcat, ssl, httpservice, custom authentication, etc. I've always reported these to customer service and logged them as bugs, so perhaps they will be addressed in a future version of Flex. Then again, these types of bugs so easily fall in a sea of finger pointing, non-trivial test case setups, and passing the buck. ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/nhFolB/TM --------------------------------------------------------------------~-> -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Web site design development Software design and development Macromedia flex Software development best practice YAHOO! GROUPS LINKS  Visit your group "flexcoders" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.