tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Turner, John" <JTur...@AAS.com>
Subject RE: MOD_JK Problem ?
Date Mon, 24 Jun 2002 11:46:51 GMT

Well said, and I agree 100%.  I spent 8 business days trying to get Apache 2
with Tomcat 4 working, both with mod_webapp and mod_jk, before giving up and
going back to Apache 1.3.  Granted, I am not experienced with tomcat, which
may account for some of the delay, but your comments are right on the money.

All due respect to the developers, but the idea that Apache 2, Tomcat 4, and
the connectors are all separate projects, with little or no coordination (as
far as I can tell) is really disappointing.  To me, that seems like a big
mistake.

John Turner
jturner@NOSPAMaas.com

-----Original Message-----
From: Andy Eastham [mailto:andy.eastham@gliant.com]
Sent: Friday, June 21, 2002 6:26 PM
To: Tomcat Users List
Subject: RE: MOD_JK Problem ?


I think everyone who uses Tomcat should back off using Apache2 until all the
connectors and more so the documentation get beyond pre-alpha state.

I'm a big fan of Apache and Tomcat, but I'm afraid the current state of the
connectors SUCKS.

I've held my tongue from writing this email for over a month, but now I
can't help it. I've wasted days trying to get this working myself, and I've
downgraded back to apache 1 again...

Given that Apache Tomcat is the reference Servlet Implementation, I think
that something needs to be done soon.  You basically can't use it with the
world's most popular web server.  It seems to me that there is very little
co-ordination between the separate Apache, Tomcat and Apache-Tomcat
connectors projects. Just take a look under
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/ - apart from
coyote, there is rather a sad dearth of content.

I'm very sorry to have written this message which I'm sure will offend some
very hard working people.  I don't want to offend anyone, but I think
someone needs to say this.  The Apache organisation has set and achieved
some very high standards, and this area is significantly below par.

Sorry.

Andy

> -----Original Message-----
> From: Jerry Jalenak [mailto:Jerry.Jalenak@LABONE.com]
> Sent: 21 June 2002 14:03
> To: 'Tomcat Users List'
> Subject: RE: MOD_JK Problem ?
>
>
> Sounds like I need to back off from 4.1.3beta and go back to the
> last 4.0.x
> build.
>
> Thanks!
>
> Jerry Jalenak
>
> -----Original Message-----
> From: Turner, John [mailto:JTurner@AAS.com]
> Sent: Friday, June 21, 2002 7:58 AM
> To: 'Tomcat Users List'
> Subject: RE: MOD_JK Problem ?
>
>
>
> According to this thread, there seems to be a problem with mod_jk and the
> latest apache (2.0.39):
>
> http://mailman.real-time.com/pipermail/tomcat-users/2002-June/069534.html
>
> John Turner
> jturner@aas.com
> http://www.aas.com
>
>
> -----Original Message-----
> From: Jerry Jalenak [mailto:Jerry.Jalenak@LABONE.com]
> Sent: Thursday, June 20, 2002 7:50 PM
> To: 'tomcat-user@jakarta.apache.org'
> Subject: MOD_JK Problem ?
>
>
> All,
>
> I've been trying to get the following configuration to work.
>
> 	Windows NT
> 	Apache 2.0.39
> 	Tomcat 4.1.3 beta
>
> Separately, I can see the Apache default 'Welcome' by going to
> http://localhost; in a similar vein I can see Tomcat's default
> 'Welcome' by
> going to http://localhost:8080/index.jsp.  What I can't make work
> is seeing
> Tomcat's 'Welcome' page by going to http://localhost/index.jsp
> (or any other
> path for that matter!).  I've rebuilt the connectors for Tomcat, download
> the mod_jk.dll from www.acg-gmbh.de/mod_jk, and set up my
> workers.properties
> and mod_jk.conf files (similar to what I used under Tomcat 3.3.1
> - maybe the
> problem?)  Does anyone have any ideas why I can't see my JSP pages without
> needing to specify the port?
>
> Thanks in advance!
>
> Jerry
>
> This transmission (and any information attached to it) may be confidential
> and is intended solely for the use of the individual or entity to which it
> is addressed. If you are not the intended recipient or the person
> responsible for delivering the transmission to the intended recipient, be
> advised that you have received this transmission in error and
> that any use,
> dissemination, forwarding, printing, or copying of this information is
> strictly prohibited. If you have received this transmission in
> error, please
> immediately notify LabOne at (800)388-4675.
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:tomcat-user-help@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:tomcat-user-help@jakarta.apache.org>
>
>



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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message