Return-Path: Delivered-To: apmail-community-archive@apache.org Received: (qmail 45142 invoked by uid 500); 27 Jun 2003 15:09:02 -0000 Mailing-List: contact community-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: community@apache.org Delivered-To: mailing list community@apache.org Received: (qmail 45022 invoked from network); 27 Jun 2003 15:09:01 -0000 Received: from adsl-63-201-231-90.dsl.snfc21.pacbell.net (HELO costin.wyn.org) (63.201.231.90) by daedalus.apache.org with SMTP; 27 Jun 2003 15:09:01 -0000 Received: by costin.wyn.org (Postfix, from userid 1107) id 029D8100E2C; Fri, 27 Jun 2003 08:08:53 -0700 (PDT) Date: Fri, 27 Jun 2003 08:08:52 -0700 (PDT) From: Costin Manolache X-X-Sender: costin@costin.wyn.org To: Apache Community Cc: Stefano Mazzocchi Subject: Re: How ASF membership works and what it means In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 27 Jun 2003, Pier Fumagalli wrote: > Now, if we put a JVM inside the Apache process scope, we end up with the > same problem we had with Apache 1.3, how in the world am I going to be able > to share a session between a JVM inside a multithreaded process A and the > clone of that same JVM inside another multithreaded process B ???? The solution is to treat Apache 2.0 processes just like a worker pool, and use the load balancing code. Requests without a session will be resolved by the in-process VM. Requests with a session will be forwared to the right VM if necesary. Apache2 will manage the creation of new workers - after all that's the benefit of multi-process, multi-thread env. Most of the times you have few processes, each with multiple threads, just like the load balanced tomcat case. Costin --------------------------------------------------------------------- To unsubscribe, e-mail: community-unsubscribe@apache.org For additional commands, e-mail: community-help@apache.org