How To Redirect a URL
I am fairly new to configuring apache web servers. Currently, I have a vanity url set up in an Apache Load Balancer and that goes to a WebLogic Cluster running a portal website. I would like to redirect this url to an antivirus server first. The antivirus server will do its thing and if it's clean, it will direct it to the portal that's running the WebLogic Cluster. What's the best way to redirect the url that is running on the apache load balancer to the antivirus server? Thank you for any information that can be provided. Regards,
Re: How To Redirect a URL
Thank you On Wed, Jun 18, 2014 at 12:40 PM, Mark Eggers its_toas...@yahoo.com.invalid wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/18/2014 9:20 AM, Lou Henry wrote: I am fairly new to configuring apache web servers. Currently, I have a vanity url set up in an Apache Load Balancer and that goes to a WebLogic Cluster running a portal website. I would like to redirect this url to an antivirus server first. The antivirus server will do its thing and if it's clean, it will direct it to the portal that's running the WebLogic Cluster. What's the best way to redirect the url that is running on the apache load balancer to the antivirus server? Thank you for any information that can be provided. Regards, This is the Apache Tomcat mailing list. I think the mailing list you're interested in is the Apache HTTPD mailing list. That said, take a look at Redirect directives that are provided with mod_alias. . . . just my two cents /mde/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTocEMAAoJEEFGbsYNeTwtMSEH/20uEFalT3abwgH3BA+p1ZxL u1dpvuPNii1TpobD+nXr9Ca6+dDofyjKR6wyesPPQse7gH/2I2z0KNzc9fvjUhNr 2HSbcPuIryvsjeGSnfLFa/GAetqxAab75WJ/E4J+BR9E0WNGlw3RpksTAYh+IELe KnMvicMZTDQAtHh5STouhAybBiQgBfMyCbpWjRaXnueq4o1NgqRsoS5RwmCgkRQx BXTo2CyOQ3ZI10X5YtdkDv89TYiB8LEmjPKeqKamYUYnWVhaFKxTNzxYbrimoW8S OMSfG0OrxxuhFTchy9KxRzwgYi58sCUSs3R8rEXq2kFpDMF5cgHoDzjwjX2m2Fc= =jfa/ -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: ServletException including path '/WEB-INF/layouts/standard.jsp'.
Thanks for responding. 1. Why such an old version? This is what the product was distributed with. 2. Does the above file exist and is readable (in the exploded war)? Yes, the file exist in ...tomcat/webapps/[appname]/WEB-INF/layouts/standard.jsp 3. The server logs may contain a more detailed message than this Error 500 page. The tomcat server logs only show informational messages of this kind: Feb 8, 2013 12:12:53 PM org.apache.jasper.compiler.TldLocationsCache tldScanJar INFO: No TLD files were found in [jndi:/localhost/[appname]/WEB-INF/lib/spring-asm-3.0.3.RELEASE.jar]. Consider adding the JAR to to the tomcat.util.scan.DefaultJarScanner.jarsToSkip in CATALINA_BASE/catalina.properties On Fri, Feb 8, 2013 at 1:07 PM, Konstantin Kolinko knst.koli...@gmail.comwrote: 2013/2/8 Lou Henry louzt...@gmail.com: Hi, I am at a complete loss with this error. I am running Apache Tomcat/ 7.0.14. 1. Why such an old version? I attempted to re-deploy a backup copy of war files that were previously working. I did not make any changes to the content of any files. I stopped Tomcat, blew away the tomcat/work/* and tomcat/temp/* files. I deleted the war and webapp directories from tomcat/webapps. I copied in the backup copy of the war files and started Tomcat to explode the wars. I attempted to access the app and received the trace listed below. Can someone please help me with this issue. Thank you... to me *HTTP Status 500 - * -- *type* Exception report *message* *description* *The server encountered an internal error () that prevented it from fulfilling this request.* *exception* org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.apache.tiles.impl.CannotRenderException: ServletException including path '/WEB-INF/layouts/standard.jsp'. 2. Does the above file exist and is readable (in the exploded war)? 3. The server logs may contain a more detailed message than this Error 500 page. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: ServletException including path '/WEB-INF/layouts/standard.jsp'.
On Fri, Feb 8, 2013 at 2:05 PM, Mark Eggers its_toas...@yahoo.com wrote: On 2/8/2013 10:29 AM, Lou Henry wrote: Thanks for responding. 1. Why such an old version? This is what the product was distributed with. 2. Does the above file exist and is readable (in the exploded war)? Yes, the file exist in ...tomcat/webapps/[appname]/**WEB-INF/layouts/standard.jsp 3. The server logs may contain a more detailed message than this Error 500 page. The tomcat server logs only show informational messages of this kind: Feb 8, 2013 12:12:53 PM org.apache.jasper.compiler.**TldLocationsCache tldScanJar INFO: No TLD files were found in [jndi:/localhost/[appname]/**WEB-INF/lib/spring-asm-3.0.3.**RELEASE.jar]. Consider adding the JAR to to the tomcat.util.scan.**DefaultJarScanner.jarsToSkip in CATALINA_BASE/catalina.**properties On Fri, Feb 8, 2013 at 1:07 PM, Konstantin Kolinko knst.koli...@gmail.comwrote: 2013/2/8 Lou Henry louzt...@gmail.com: Hi, I am at a complete loss with this error. I am running Apache Tomcat/ 7.0.14. 1. Why such an old version? I attempted to re-deploy a backup copy of war files that were previously working. I did not make any changes to the content of any files. I stopped Tomcat, blew away the tomcat/work/* and tomcat/temp/* files. I deleted the war and webapp directories from tomcat/webapps. I copied in the backup copy of the war files and started Tomcat to explode the wars. I attempted to access the app and received the trace listed below. Can someone please help me with this issue. Thank you... to me *HTTP Status 500 - * -- *type* Exception report *message* *description* *The server encountered an internal error () that prevented it from fulfilling this request.* *exception* org.springframework.web.util.**NestedServletException: Request processing failed; nested exception is org.apache.tiles.impl.** CannotRenderException: ServletException including path '/WEB-INF/layouts/standard.**jsp'. 2. Does the above file exist and is readable (in the exploded war)? 3. The server logs may contain a more detailed message than this Error 500 page. Best regards, Konstantin Kolinko Does this application depend on additional jars in $CATALINA_HOME/lib (bad practice in general)? Did the war file contain a META-INF/context.xml? If so, did you delete conf/Catalina/localhost/app-**name.xml? This is assuming that you've not renamed the Service name and default host of course. . . . . just my two (previously bitten on this) cents. /mde/ I've seen these Informational jar messages before; but, the application ran successfully; so, I don't think the app depend on the additional jars in $CATALINA_HOME/lib. There is no context.xml in META-INF and there's nothing in conf/Catalina/localhost Thank you, --**--**- To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.orgusers-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Sticky sessions not working
Thank you all for your responses. We found that sticky was set up properly. The problem was with the application and how it handles clustering. Thanks again... On Fri, Sep 21, 2012 at 11:51 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicolas, On 9/21/12 12:58 AM, Nicolas Sarazin wrote: Add : worker.node1.route=node1 And : worker.node2.route=node2 To use sticky session. These directives attach name route at the end of JSESSIONID. That shouldn't be necessary, as the worker's name is the default 'route', and the OP has them set up properly. I think this might be interfering with your setup: Le vendredi 21 septembre 2012, Lou Henry a écrit : worker.node1.domain=jvm1 worker.node2.domain=jvm2 Lou, do you need the domain for anything? The docs say that when sticky_session=true (which is the default, and you haven't overridden it), then the domain becomes the 'route'. Since you aren't explicitly specifying the route, then you are probably getting implicitly: worker.node1.route=jvm1 worker.node2.route=jvm2 when what you want is 'node1' and 'node2'. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBdNa0ACgkQ9CaO5/Lv0PBMFwCfQZdAuuEH+FNiwli6n7+dk22B 6/4AoIk1i4MnH3qglv8pah5xY47Jzos+ =EA2N -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Sticky sessions not working
I'm running Apache Tomcat 7.0.14 and Apache 2.2.21 (mod_jk1.2.37). I am trying to load balance two Tomcat Servers and sticky sessions are not working. I am running a two-factor authentication package and it looks like my LB configuration is directing the user to one Tomcat for part of the transaction and to the other Tomcat server for the other part. When I bring down one of the Tomcat servers, everything works fine; but with both Tomcat servers up, I get 500 errors. So, I am trying to stick the webserver session to one particular Tomcat server. Listed below is my configuration. Also, I tried without the domain directive also. I am not quite sure if that's a random name or should it be something specific. Can someone please assist? Thank you... *workers.properties* worker.list=loadbalancer,status # Define Node1 # modify the host as your host IP or DNS name. worker.node1.domain=jvm1 worker.node1.port= worker.node1.host=t*20.x. worker.node1.type=ajp13 worker.node1.lbfactor=1 worker.node1.ping_mode=A # Define Node2 # modify the host as your host IP or DNS name. worker.node2.domain=jvm2 worker.node2.port= worker.node2.host=t*21.x. worker.node2.type=ajp13 worker.node2.lbfactor=1 worker.node2.ping_mode=A # Load-balancing behaviour worker.loadbalancer.type=lb worker.loadbalancer.balance_workers=node1,node2 worker.loadbalancer.sticky_session=True # Status worker for managing load balancer worker.status.type=status # Added per Anakam direction 113010 worker.node1.socket_keepalive=True worker.node1.socket_timeout=300 # Added per Anakam direction 113010 worker.node2.socket_keepalive=True worker.node2.socket_keepalive=300 *server.xml on Tomcat Node 1* Engine name=Catalina defaultHost=localhost jvmRoute=node1 *server.xml on Tomcat Node 2* Engine name=Catalina defaultHost=localhost jvmRoute=node2
