Hi all,
I've a jsp-based application (interface to an oracle db) that will go in
production in January. The server is actually configured this way:
SuSe 9.0, Apache 2.0.48 (with a virtual host redirecting everything to
Tomcat), Tomcat-5.0.28, configured with mod_jk2 because I read that md_jk2
[EMAIL PROTECTED] wrote:
I read (by chance?) somewhere on the jakarta web site that mod_jk2 (aka
JK2) is officially unsupported since mid-November.
Well, it is actually not supported for a much longer time :).
At this point I'm not sure what to do: should I use JK? Should I stay with
mod_jk2
The recommended ways to go are JK or mod_proxy_ajp.
Ta
Matt
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 20 December 2004 11:17
To: [EMAIL PROTECTED]
Subject: mod_jk2 future?
Hi all,
I've a jsp-based application (interface to an oracle db) that will go
On Mon, Dec 20, 2004 at 12:16:51PM +0100, [EMAIL PROTECTED] wrote:
: Tomcat), Tomcat-5.0.28, configured with mod_jk2 because I read that md_jk2
: was the connector to use with apache 2.x.x
Where did you read this?
I ask because plain mod_jk (aka version 1) works just fine with Apache
2.x. A
Actually I don't remember.
When we decided to use Tomcat instead of Websphere a few months ago, I
read quite a lot of documentation/articles (I'm not a developer, but the
systems' administrator of our linux servers). I just remember reading the
following line because I saved it: jk2 is a
On Mon, Dec 20, 2004 at 02:02:56PM +0100, [EMAIL PROTECTED] wrote:
: I will check with the developpers team whether switching from JK2 to JK
: could be a problem but is there any known issues in switching from one
: connector to the other (apart for the configuration files)
I can't say, as I've
