Apache Conf File: LoadModule jk_module modules/mod_jk.so
JkWorkersFile /usr/local/tomcat/conf/workers.properties JkLogFile /usr/local/tomcat/logs/jk.log JkShmFile logs/jk.shm JkLogLevel warn # Note : Change webapp to the name of your web application Alias /webapp "/usr/local/tomcat/webapps/webapp" <Directory "/usr/local/tomcat/webapps/webapp"> Options Indexes FollowSymLinks DirectoryIndex index.html index.jsp </Directory> # If you don't add at least one mount, you get nothing: JkMount /webapp/*.jsp ajp13 JkMount /webapp/*.mxml ajp13 JkMount /webapp/flex* ajp13 JkMount /webapp/flash* ajp13 #Note: The above is intended to allow tomcat to serve the dynamic # pages and apache to serve the static pages/images. # But it is much easier to simply let tomcat serve everything in # the webapp initially. The following line allows this. JkMount /webapp/* ajp13 ---------------------------- # workers.properties - # # This file provides jk derived plugins with the needed information to # connect to the different tomcat workers. Note that the distributed # version of this file requires modification before it is usable by a # plugin. # # As a general note, the characters $( and ) are used internally to define # macros. Do not use them in your own configuration!!! # # Whenever you see a set of lines such as: # x=value # y=$(x)\something # # the final value for y will be value\something # # Normaly all you will need to do is un-comment and modify the first three # properties, i.e. workers.tomcat_home, workers.java_home and ps. # Most of the configuration is derived from these. # # When you are done updating workers.tomcat_home, workers.java_home and ps # you should have 3 workers configured: # # - An ajp12 worker that connects to localhost:8007 # - An ajp13 worker that connects to localhost:8009 # - A jni inprocess worker. # - A load balancer worker # # However by default the plugins will only use the ajp12 worker. To have # the plugins use other workers you should modify the worker.list property. # # # OPTIONS ( very important for jni mode ) # # workers.tomcat_home should point to the location where you # installed tomcat. This is where you have your conf, webapps and lib # directories. # workers.tomcat_home=/usr/local/tomcat # # workers.java_home should point to your Java installation. Normally # you should have a bin and lib directories beneath it. # workers.java_home=/usr/local/java # # You should configure your environment slash... ps=\ on NT and / on UNIX # and maybe something different elsewhere. # ps=/ # #------ ADVANCED MODE ------------------------------------------------ #--------------------------------------------------------------------- # # #------ DEFAULT worket list ------------------------------------------ #--------------------------------------------------------------------- # # # The workers that your plugins should create and work with # # Add 'inprocess' if you want JNI connector worker.list=ajp13 # , inprocess # #------ DEFAULT ajp12 WORKER DEFINITION ------------------------------ #--------------------------------------------------------------------- # # # Defining a worker named ajp12 and of type ajp12 # Note that the name and the type do not have to match. # worker.ajp12.port=8007 worker.ajp12.host=localhost worker.ajp12.type=ajp12 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # ----> lbfactor must be > 0 # ----> Low lbfactor means less work done by the worker. worker.ajp12.lbfactor=1 # #------ DEFAULT ajp13 WORKER DEFINITION ------------------------------ #--------------------------------------------------------------------- # # # Defining a worker named ajp13 and of type ajp13 # Note that the name and the type do not have to match. # worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # ----> lbfactor must be > 0 # ----> Low lbfactor means less work done by the worker. worker.ajp13.lbfactor=1 # # Specify the size of the open connection cache. #worker.ajp13.cachesize # #------ DEFAULT LOAD BALANCER WORKER DEFINITION ---------------------- #--------------------------------------------------------------------- # # # The loadbalancer (type lb) workers perform wighted round-robin # load balancing with sticky sessions. # Note: # ----> If a worker dies, the load balancer will check its state # once in a while. Until then all work is redirected to peer # workers. worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=ajp12, ajp13 # #------ DEFAULT JNI WORKER DEFINITION--------------------------------- #--------------------------------------------------------------------- # # # Defining a worker named inprocess and of type jni # Note that the name and the type do not have to match. # worker.inprocess.type=jni # #------ CLASSPATH DEFINITION ----------------------------------------- #--------------------------------------------------------------------- # # # Additional class path components. # worker.inprocess.class_path=$(workers.tomcat_home)$(ps)lib$(ps)tomcat.jar # # Setting the command line for tomcat. # Note: The cmd_line string may not contain spaces. # worker.inprocess.cmd_line=start # Not needed, but can be customized. #worker.inprocess.cmd_line=-config #worker.inprocess.cmd_line=$(workers.tomcat_home)$(ps)conf$(ps)server.xml #worker.inprocess.cmd_line=-home #worker.inprocess.cmd_line=$(workers.tomcat_home) # # The JVM that we are about to use # # This is for Java2 # # Windows #worker.inprocess.jvm_lib=$(workers.java_home)$(ps)jre$(ps)bin$(ps)classic$(ps)jvm.dll # IBM JDK1.3 #worker.inprocess.jvm_lib=$(workers.java_home)$(ps)jre$(ps)bin$(ps)classic$(ps)libjvm.so # Unix - Sun VM or blackdown worker.inprocess.jvm_lib=$(workers.java_home)$(ps)jre$(ps)lib$(ps)amd64$(ps)server$(ps)libjvm.so # # And this is for jdk1.1.X # #worker.inprocess.jvm_lib=$(workers.java_home)$(ps)bin$(ps)javai.dll # # Setting the place for the stdout and stderr of tomcat # worker.inprocess.stdout=$(workers.tomcat_home)$(ps)logs$(ps)inprocess.stdout worker.inprocess.stderr=$(workers.tomcat_home)$(ps)logs$(ps)inprocess.stderr # # Setting the tomcat.home Java property # #worker.inprocess.sysprops=tomcat.home=$(workers.tomcat_home) # # Java system properties # # worker.inprocess.sysprops=java.compiler=NONE # worker.inprocess.sysprops=myprop=mypropvalue # # Additional path components. # # worker.inprocess.ld_path=d:$(ps)SQLLIB$(ps)bin # --- In [email protected], "charlespaz1" <[EMAIL PROTECTED]> 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 [email protected], "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/[email protected]/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 --------------------~--> Most low income households are not online. Help bridge the digital divide today! http://us.click.yahoo.com/cd_AJB/QnQLAA/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/
