tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Lowe <>
Subject Re: connectors documents
Date Wed, 01 Oct 2003 10:45:20 GMT
Okay.. I'm trying to stick with jk, but jk2 is there as an option also. 
Everything's running in terms of calling the mounted contexts over port 
80 and life it great and all that.

Now.. Is there a recommended method of  mapping a jk mount as the 
document root of a virtual host? The stuff in the jk2 example looked 
the business, but jk2 doesn't seem to like the [uri:[vhost]:[port]] 
stuff.. I'm continuing down the jk road as efforts to conquer this 
beast, I just have trouble believing that nobody has this running and 
could enlighten me.

Cheers Mark

On Wednesday, October 1, 2003, at 11:20 AM, Walker Chris wrote:

> Sadly, I have to agree with Mark.
> Last week Tim Funk suggested I RTFAQ to find out why not to use 
> mod_webapp.
> Though well-meant, this suggestion was regrettable from my point of 
> view as
> I was 24 hours from a go-live with webapp (having read in a
> highly-recommended Tomcat book that webapp is the only way to go).  So 
> I
> spent a day trying to get mod_jk(2) to work on my server (Sun Cobalt 
> Raq550,
> Apache 1.3, Tomcat 4.1), followed by a night putting webapp back.
> Unless I've missed an important part, the JK section on the Tomcat 
> site is
> frustratingly vague.  There are lots of snippets from config files, but
> there's no hard specification of what the elements in these files do 
> and how
> they inter-relate.  Examples are useful, but examples alone are like 
> giving
> a hungry man a fish rather than a rod.
> I know this stuff is all produced by magnificent voluntary effort, and 
> I
> also know that documentation is the armpit (to be polite) of software
> development.  But if the software isn't well-documented then the 
> effort that
> went into producing it is largely wasted...
> Regards
> Chris
> -----Original Message-----
> From: Mark Lowe []
> Sent: 01 October 2003 10:13
> To: Tomcat Developers List
> Cc:
> Subject: Re: connectors documents
> Yeah i know,
> I did.. and now i'm trying a cheeky question to the dev list..
> They seem to be more interested in other stuff on the user list..
> Given that both tomcat and apache are so great i'm surprised that they
> continue to be plagued by this connector business. How many years now?
> , I'm not sure, but if there was reason not to use these technologies
> then connectors would be it..
> I thought a mail to the folks who are involved with this stuff could be
> the way forward. Its great to see an example on jk2 and vhosts , it
> would be even better if it worked.
> So to repeat my question on both lists..
> Is there any documentation, on jk, jk2 or mod_webapp that explains
> configuring vhosts in a sensible manner that doesn't just go as far as
> http://domain/webappname .. because frankly that bit is easy, and
> suffers from chocolate fire-guard syndrome in terms of it utility.
> If not i would be eternally grateful if anyone could take me through
> this, especially if you have a real server in the real world , really
> doing this.. I dont care which connector, protocol whatever. If this
> does work and if i'm being a dofuss then feedback would be useful..
> does this work? Looks like there are 3 files that need amending just to
> administer it, but i'll live with it.. So far apache cant find the
> I have no idea why or how to find out why..
> Many thanks in advance
> Mark
> On Wednesday, October 1, 2003, at 09:47 AM, David Rees wrote:
>> On Wed, October 1, 2003 at 1:18 am, Mark Lowe sent the following
>>> Despite using tomcat for 3-4 years jakarta connectors has remained 
>>> the
>>> moving goal post. I dont usually have the pleasure of having to get
>>> tomcat and apache talking to one another, but i do now.
>> <snip>
>> Subject is really for tomcat-users list.  Post the question there and
>> I'll
>> try to answer.
>> -Dave
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message