Matthew,

In my environment, I wanted to force all contexts to be in the root context.

So, my point is -- if you only need the root context (one context only!), my
kludge works.  If you want root context and non-root contexts to both
coexist, then you'll need to modify my kludge to NOT force the context to
the root context.  You'll have to test it to see if it works for you
(because I haven't). I think Andrew Cowie did the latter (not force the
contexts to the root context), but I don't want to speak for him.

If you need multiple contexts without the root context, then the existing
Tomcat should be perfectly fine.

Joseph
-----Original Message-----
From: Matthew Dornquast [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 09, 2000 2:28 PM
To: [EMAIL PROTECTED]
Subject: Re: No revolution today


> Well, but if you don't need the root-context, then the load balancing
> *should* work with other contexts.  You are using mod_jserv with APJ
> Balancesets, right?

Right Jospeh!

So how important is it to support load balancing of root contexts?

How many users use the root context?

>From where I sit, it's a requirement, I have no other option.

I don't want to go into the reasons as to why this is, (Unless there is a
great deal of interest)
but I do wonder how many others are doing it like I am?

> its a big change. fix for 3.3 ? This would seriously nuke loadbalancing
> for 3.2 if something was screwed up. besides, i'd rather see 3.2 stable
> out after so many months (years?).

I wish I knew if it was a big change or not.

When I was trying to do it, it felt like it was more of a mod_jserv issue
and had little/nothing to do with tomcat.

It seemed like mod_serv config parser just couldn't grok what I was telling
it.

(Kudos to the designer(s) of the API for mod_jserv, I thought it well
thought out and
easy to config given the amount of power/flexibility they were giving me.)

3.2 Stable is very important, at a minimum however, documentation should be
updated to state it's not supported in 3.2 root context.

-matthew





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to