Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <433AFD9F.8030407@apache.org>
Date: Wed, 28 Sep 2005 21:31:27 +0100
From: Mark Thomas <markt@apache.org>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: Vexing Problem with Tomcat connector
References: <76f67017e4567a459e70b5614f3ec5b5@mailserv.crossref.org>
In-Reply-To: <76f67017e4567a459e70b5614f3ec5b5@mailserv.crossref.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

When starting a new thread (ie sending a message to the list about a 
new topic) please do not reply to an existing message and change the 
subject line. To many of the list archiving services and mail clients 
used by list subscribers this  makes your new message appear as part 
of the old thread. This makes it harder for other users to find 
relevant information when searching the lists.

This is known as thread hijacking and is behaviour that is frowned 
upon on this list. Frequent offenders will be removed from the list. 
It should also be noted that many list subscribers automatically 
ignore any messages that hijack another thread.

The correct procedure is to create a new message with a new subject. 
This will start a new thread.

Mark
tomcat-user-owner

tpickard@crossref.org wrote:
> Hello,
> 
> I have a website that I am migrating to a new server.
> 
> Server is Redhat ES3 2.4.21-20.0.1.ELsmp.  Server version: Apache/2.0.46
> 
> I have jakarta-tomcat-5.5.9 installed and working properly on the new
> server.  It is perfectly accessible from the legacy web server.  
> 
> On the Website on the new server, access to jsp based pages give a 503
> error.
> 
> The main page, home.jsp, loads fine in the servlet if no page is given.
> http://webserver/PI/  The home.jsp spawns a 503 if is in the URL.
> http://webserver/PI/home.jsp   I can successfully get images from the
> page from the tomcat instance.  It does not like the .jsp extension.
> 
> In the mod_jk log i can see the match made:
> [Wed Sep 28 10:29:14 2005] [18841:2816] [debug]
> map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context
> URI '/PI/*'
> [Wed Sep 28 10:29:14 2005] [18841:2816] [debug]
> map_uri_to_worker::jk_uri_worker_map.c (475): Found a wildchar match
> worker3 -> /PI/*
>                           
> However, in the apache access log is the 503. 
> xxx.89.23.173 - - [28/Sep/2005:10:29:14 -0400] "GET /PI/home.jsp
> HTTP/1.1" 503 412 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
> rv:1.7.12) Gecko/20050915 Firefox/1.0.7"
> SESSIONID=128F9AD992A16BC3D3EB1ED0AD5549C1
> 
> I have watched in Ethereal as no traffic goes from the apache to the
> tomcat.
> I have tried using the loopback and local network address.
> I have tried adding a *.jsp directive to the mod_jk config for the
> servlet.
> 
> Any help would be appreciated.  I have a dent in my desk from hitting it
> with my forehead.
> 
> Apache Config:
> 
> #INSERT OF TOMCAT CONF PARAMETERS
> # Load mod_jk module
> # LoadModule jk_module modules/mod_jk.so
> LoadModule jk_module /etc/httpd/modules/mod_jk.so
> 
> # Declare the module for <IfModule directive>
> #AddModule mod_jk.c
> 
> # Where to find workers.properties
> JkWorkersFile /etc/httpd/conf/workers.properties
> 
> # Where to put jk logs
> JkLogFile /var/log/httpd/mod_jk.log
> 
> # Set the jk log level [debug/error/info]
> JkLogLevel debug
> 
> # Select the log format
> JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
> 
> # JkOptions indicate to send SSL KEY SIZE,
> JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
> 
> # JkRequestLogFormat set the request format
> JkRequestLogFormat "%w %V %T"
> 
> # Send servlet for context /examples to worker named worker1
> JkMount /examples/servlet/* worker1
> JkMount /PI/* worker3
> #JkMount /PI/*.jsp worker3
> # Send JSPs for context /examples to worker named worker1
> JkMount /examples/*.jsp worker1
> JkMount /journals/*.jsp worker1
> 
> Worker Properties
> /etc/httpd/conf/workers.properties
> # Define some properties
> workers.apache_log=/var/log/httpd/ 
> workers.tomcat_home=/usr/local/tomcat/jakarta-tomcat-5.5.9 
> workers.java_home=/usr/bin/java
> ps=/ 
> 
> #  
> worker.list=worker1 
> 
> # Set properties for worker1 (ajp13)
> worker.worker1.type=ajp13
> worker.worker1.host=172.20.1.19
> worker.worker1.port=8009
> 
> #
> worker.list=worker2
> 
> # Set properties for worker2 (ajp13)
> worker.worker2.type=ajp13
> worker.worker2.host=172.20.1.19
> worker.worker2.port=10009
> 
> #
> worker.list=worker3
> 
> # Set properties for worker3 (ajp13)
> worker.worker3.type=ajp13
> worker.worker3.host=127.0.0.1
> worker.worker3.port=8099
> 
> #
> worker.list=worker4
> 
> # Set properties for worker4 (ajp13)
> worker.worker4.type=ajp13
> worker.worker4.host=172.20.1.19
> worker.worker4.port=8099
> 
> 
> _____________________________________
> 
> Tim Pickard
> CrossRef 
> Systems Support Analyst and Administrator
> 40 Salem Street
> Lynnfield, MA 01940
> tpickard at crossref dot org
> 781 295 0072 x27
> ______________________________________
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org