I've done some work with this, and session routing now works fine for
both root and non-root contexts as far as I can tell. These changes
were committed for 3.2b7. I've done my testing with mod_jk and AJP12.
mod_jk provides the lbworker type which seems to work perfectly for me
but there is no
Joseph Chiu [mailto:[EMAIL PROTECTED]] wrote:
> 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.
We are presently employing Joseph's elegant (we force root context o
> In our situation, we plan to use multiple virtual hosts, each with its
> own root context. That makes the URLs shorter and easier for people to
> work with. It also lets you more easily move/copy one context to
> another without having to fix all the links.
We use many virtual hosts today in
t, 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 r
[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
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 lo
> 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
En réponse à Paulo Gaspar <[EMAIL PROTECTED]>:
> But at the moment, for me, my company and people/companies I know, the
> ONE
> main priority is having a fast and robust Servlet Engine - with robust
> being the priority.
+1
> Your focus on a modular architecture keeps all doors open for the
> d
PM
To: [EMAIL PROTECTED]
Subject: Re: No revolution today
On Thu, 9 Nov 2000, Matthew Dornquast wrote:
> re>Our site (http://www.spun.com) runs multiple Apache servers with load
> balancers ("rotator box like BigIP") that distribute traffic over the
Apache
> servers. We ha
On Thu, 9 Nov 2000, Matthew Dornquast wrote:
> re>Our site (http://www.spun.com) runs multiple Apache servers with load
> balancers ("rotator box like BigIP") that distribute traffic over the Apache
> servers. We have a farm of Tomcat servers. The session API's work for us.
> The only problem
re>Our site (http://www.spun.com) runs multiple Apache servers with load
balancers ("rotator box like BigIP") that distribute traffic over the Apache
servers. We have a farm of Tomcat servers. The session API's work for us.
The only problem is that Tomcat, as distributed, does not allow load
bal
IL PROTECTED]
Subject: Re: No revolution today
On Thu, 9 Nov 2000, Henri Gomez wrote:
> > It is important that tomcat3 has a design that allows support for
> > future
> > versions of the servlet API, but if tomcat developers don't want to see
> > it
> > happ
On Thu, 9 Nov 2000, Matthew Dornquast wrote:
> > umm...it does. i use it.
> > -Ys-
>
> My understanding is it DOES work for app contexts mapped to a URL like
> "/myapp" but it does NOT work
> for the root context. "/"
>
> Many of us have webapps that mount to the root context.
>
> I spent W
On Thu, 9 Nov 2000, Nick Bauman wrote:
>
> How? As far as I can tell it's broken in TC 3.1 / mod_jserv. Can you
> describe your configuration?
>
>
> > > "as advertised" in a web server farm with a rotator box like BigIP. Right
> > > now the Session API in tomcat 3.1 /does not work/ across mu
> umm...it does. i use it.
> -Ys-
My understanding is it DOES work for app contexts mapped to a URL like
"/myapp" but it does NOT work
for the root context. "/"
Many of us have webapps that mount to the root context.
I spent WAY to much time figuring this out, I'd love to be proven wrong.
But
How? As far as I can tell it's broken in TC 3.1 / mod_jserv. Can you
describe your configuration?
On Thu, 9 Nov 2000, [EMAIL PROTECTED] wrote:
>
>
> On Wed, 8 Nov 2000, Nick Bauman wrote:
>
> > On Thu, 9 Nov 2000, Henri Gomez wrote:
> >
> > > > It is important that tomcat3 has a design that
>
> I for one, would love to see the 3.x codebase's Session API actually work
> "as advertised" in a web server farm with a rotator box like BigIP. Right
> now the Session API in tomcat 3.1 /does not work/ across multiple
> instances of tomcat in a server farm.
And that's why the session stuff
On Wed, 8 Nov 2000, Nick Bauman wrote:
> On Thu, 9 Nov 2000, Henri Gomez wrote:
>
> > > It is important that tomcat3 has a design that allows support for
> > > future
> > > versions of the servlet API, but if tomcat developers don't want to see
> > > it
> > > happen - so be it. When Servlet2.3
Very wise decision.
And nothing forbids you of doing those revolutions in the future.
But at the moment, for me, my company and people/companies I know, the ONE
main priority is having a fast and robust Servlet Engine - with robust
being the priority.
Your focus on a modular architecture keeps
> -Original Message-
> From: Nick Bauman [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 09, 2000 5:42 AM
> To: [EMAIL PROTECTED]
> Subject: Re: No revolution today
>
>
> On Thu, 9 Nov 2000, Henri Gomez wrote:
>
> > > It is important that tomc
On Thu, 9 Nov 2000, Henri Gomez wrote:
> > It is important that tomcat3 has a design that allows support for
> > future
> > versions of the servlet API, but if tomcat developers don't want to see
> > it
> > happen - so be it. When Servlet2.3 will be final and in wide use, there
> > is
> > nothing
> It is important that tomcat3 has a design that allows support for
> future
> versions of the servlet API, but if tomcat developers don't want to see
> it
> happen - so be it. When Servlet2.3 will be final and in wide use, there
> is
> nothing that can stop someone from providing the module that
Hi,
After a lot of thinking, I decided to give up ( at least temporary ) my
plans for a tomcat revolution. It was very tempting, but I don't think
it's the right thing to do - evolution is still the best way to go :-)
It is important that tomcat3 has a design that allows support for future
vers
23 matches
Mail list logo
