Return-Path: 
 <tomcat-user-return-53245-qmlist-jakarta-archive-tomcat-user=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org
Received: (qmail 77032 invoked from network); 13 Feb 2003 19:01:46 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 13 Feb 2003 19:01:46 -0000
Received: (qmail 27051 invoked by uid 97); 13 Feb 2003 19:03:20 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org
Received: (qmail 27044 invoked from network); 13 Feb 2003 19:03:20 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 13 Feb 2003 19:03:20 -0000
Received: (qmail 75371 invoked by uid 500); 13 Feb 2003 19:01:27 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 75333 invoked from network); 13 Feb 2003 19:01:26 -0000
Received: from myptschilsrv01.corp.mypoints.com (HELO schxchmail.mypoints.com)
 (209.141.54.201)
  by daedalus.apache.org with SMTP; 13 Feb 2003 19:01:26 -0000
Received: by myptschilxch.corp.mypoints.com with Internet Mail Service
 (5.5.2656.59)
	id <D6S6VATN>; Thu, 13 Feb 2003 13:03:38 -0600
Message-ID: 
 <F1FF357E591DD41193D300508BAC63750E2A5AB9@myptschilxch.corp.mypoints.com>
From: Brett Neumeier <brett.neumeier@ualloyalty.com>
To: 'Tomcat Users List' <tomcat-user@jakarta.apache.org>
Subject: RE: jk2 config -- uri directive for root context?
Date: Thu, 13 Feb 2003 13:03:36 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="windows-1252"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hi Jake,

> Does this work when going to Tomcat directly (say to port 8080, if you've
> got a HTTP connector listening to that port) rather than going through a
> native web server?  If you don't have an HTTP connector configured in
> Tomcat, you might want to add one to help in debugging the situation.

Have you tried this?  What happens when you take the web server and JK out
of the picture?  I think this is the most obvious first step you can take to
determine where the problem lies.

If it turns out that everything works fine when you make the request
directly to Tomcat, then the problem is certainly related to JK2 -- either a
bug in the JK2 code, or a misconfiguration, or both.

If it turns out that HTTP requests direct to Tomcat don't work any better
than the ones being sent through the native web server and JK2, then the
problem is probably not related to JK2 -- thus there must be a
misconfiguration on the Tomcat side.

> You also might want to enable debugging information in the web server, or
> tomcat, or both -- if you can find out what Tomcat is trying to do, that
> might illuminate why it's not doing what you expect.

Have you tried this?  The places you can turn on debugging information (as
far as I know) are:

In workers2.properties, as "debug=" properties for components -- you can set
debug to values from 1 to 10, according to the documentation, with higher
numbers meaning more log data.

In server.xml, as "debug=" attributes of Connector or Context elements (with
1-10 values as above).

What might be informative is to turn on debugging output for all of these,
and look over what each component thinks is happening.

Cheers,

bn

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