Re: Problem moving from HTTP to HTTPS

Thank you both. Removing the auth-constraint/ element quickly solved the problem for me. So far, I have not run into any MSIE problems with this solution, hopefully my luck will continue. (By default, users will be given https:// links anyway, the redirection is only for those who might

RE: Apache 80 Tomcat 8080

From: Propes, Barry L [EMAIL PROTECTED] Reply-To: Tomcat Users List users@tomcat.apache.org To: Tomcat Users List users@tomcat.apache.org Subject: RE: Apache 80 Tomcat 8080 Date: Fri, 1 Sep 2006 16:19:02 -0400 in the server.xml file, (in the conf dir) see if you have a line like this: !--

need help with .startup.sh

Hello: I need help figuring out how to modify my tomcat deployment so when the JVM starts it starts with a -server option. There seems to be a bug in the jvm implementation that fedoracore 4 is using and using this option when the jvm starts corrects the problem at least from my application's

RE: need help with .startup.sh

There is no need to change any of the shell scripts. You need to set environment variable JAVA_OPTS with the desired option and the tomcat scripts will pick it up automatically. The catalina.sh script looks for a script called setenv.sh to set this and other similar options. Here are the

Severe problems

Hi all, like always, time is short and we have a very critical situation here, so please help to save the day once again. I have already posted this on a PostgreSQL mailing list, but maybe it is somehow related to Tomcat. Installation facts: - 4 High Availability Clusters consisting of 2 Dual

Re: mod_jk validate failed / factory failed error

I can load your workers.properties configuration using 1.2.18 (but I Used Apache 2 and Solaris). The validate method code says, that either there should be a message of level error before the first one you copied to your mail (and that one will give us a better indication about what's wrong), or

Re: Clustering with mod_jk

You should try 1.2.18 and depending on your time frame update to 1.2.19 once it's being released this month. We improved load balancing code and with 1.2.19 also the observability of what's happening. Try the alternative method B (Busyness) for the load balancer in 1.2.18. The default method

Re: Migration from jk2 to jk, problems with uri context

What about changing worker.worker1.mount=/foo/* foo to worker.worker1.mount=/foo/* /foo Regards, Rainer james edwards schrieb: I am moving to jk (1.2.18) from jk2 am having problems with the workers.properties file. I have separate apache and tomcat servers. Here is my working jk2