Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
In-Reply-To: <42CCA751.20205@savoirtech.com>
To: dev@geronimo.apache.org
Subject: Re: Change Geronimo to use Tomcat JK 1.2.13 instead of the
 unsupported JK 2
 ?
MIME-Version: 1.0
From: sissonj@insession.com
Message-ID: 
 <OF9DD0537D.D8B2202E-ONCA257037.001FDDAB-CA257037.0026EE26@tsainc.com>
Date: Thu, 7 Jul 2005 18:05:11 +1100
Content-Type: text/plain; charset="US-ASCII"

I'm not having a problem, but have these concerns:

* we were using an old version of the JK code (files dated 15-Jan-2004) 
that appears to be different to the version of the JK code that you get in 
the Standalone Tomcat 5.5.9 file tomcat-ajp.jar (files dated 26-mar-2005). 
 I am guessing "tomcat_jk2_version=5.0.18" is the connector code taken 
from the TOMCAT_5_0_18 tag.  There have been bug fixes since then before 
the TOMCAT_5_5_9 tag:
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-connectors/jk/java/org/apache/jk/server/JkCoyoteHandler.java?rev=1.63&view=log
* the name of the JAR makes it sound like we are using the unsupported JK 
2.
* other people will ask these same questions later when they see us using 
versions of JARs out of sync and could make support of the code more 
difficult.

I propose the following:

* That a JAR called tomcat-jk-5.5.9.jar or tomcat-ajp-5.5.9 (based on the 
Tomcat 5.5.9 tomcat-ajp.jar) be uploaded to Ibiblio.  I think Jacek has 
been involved in Tomcat JAR uploads to maven before.
* Change the geronimo build to use this differently named and versioned 
file
* change the tomcat_jk2_version property in project.properties to be 
tomcat_jk_version or tomcat_ajp_version so that no one on the future 
thinks we are using the unsupported JK 2.

If people agree, I'll raise a JIRA issue.

Thanks,

John

Jeff Genender <jgenender@savoirtech.com> wrote on 07/07/2005 01:53:53 PM:

> That version was used because the AJP needs the JkCoyoteHandler. 
> Honestly, its being used because that seemed to be the latest and 
> greatest at the time (IIRC we started with Tomcat 5.0.x)...and according 

> to ibibilio, it looks like its the latest one they have for the Java 
> side. AFAIK, it seems to work fine.  If we can find a better one, or 
> this one does not work, then lets look into it.
> 
> Are you having any problems with it?
> 
> Jeff
> 
> sissonj@insession.com wrote:
> > Currently Geronimo uses the following:
> > 
> > tomcat_jk2_version=5.0.18
> > tomcat_version=5.5.9
> > 
> > According to the Jakarta Tomcat Connectors page JK2 is officially 
> > unsupported and has been put in maintainer mode and no further 
development 
> > will take place 
> > http://jakarta.apache.org/tomcat/connectors-doc/news/20041100.
> html#20041115.1 
> > .
> > 
> > Also I read the Tomcat 5.5 documentation and it says that JK1.2 is 
> > supported and "Other native connectors supporting AJP may work, but 
are no 
> > longer supported" 
> > http://jakarta.apache.org/tomcat/tomcat-5.5-doc/connectors.html. 
> > 
> > I'm also not clear what the jk2 version (5.0.18) really is, as the 
last 
> > official JK2 release is 2.0.4 according to 
> > http://jakarta.apache.org/tomcat/connectors-doc/news/20041100.html
> > 
> > Or could it be that I am being mislead by 'jk2' being i the property 
name 
> > and it isn't really JK2 ?
> > 
> > John