Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 61266 invoked from network); 7 Nov 2001 17:23:32 -0000 Received: from unknown (HELO osaka.betaversion.org) (192.18.49.133) by daedalus.apache.org with SMTP; 7 Nov 2001 17:23:32 -0000 Received: (qmail 9901 invoked from network); 7 Nov 2001 17:26:02 -0000 Received: from nagoya.betaversion.org (192.18.49.131) by osaka.betaversion.org with SMTP; 7 Nov 2001 17:26:02 -0000 Received: (qmail 16742 invoked by uid 97); 7 Nov 2001 17:21:45 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 16717 invoked by uid 97); 7 Nov 2001 17:21:45 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 16685 invoked from network); 7 Nov 2001 17:21:44 -0000 Message-ID: <028e01c167b0$b77afc00$1f00a8c0@stepston4undxv> From: "Mika Goeckel" To: "Tomcat Users List" References: <439C4B6AA81ED511ABAF00508BDFE0A6F8D67A@HOLMES07> Subject: Re: Distributed Session Managment / Clusters Date: Wed, 7 Nov 2001 18:21:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Mr. Lauer, Sir, I've recently started a discussion about improvements and further developments of the cluster package on the tomcat-dev mailing list topic "Re: Tomcat 4 Cluster -- plans?", I would appreciate if you may want to contribute there **biggrin** ^X^S^X^C or :wq? ----- Original Message ----- From: "Lauer, Oliver" To: "'Tomcat Users List'" ; "'Tom Drake'" Sent: Wednesday, November 07, 2001 6:12 PM Subject: AW: Distributed Session Managment / Clusters > cool :-) I'll try the same. > > > AXA eSolutions GmbH > > AXA Konzern AG Germany > > Oliver Lauer > > Web Architect > > W�rthstra�e 34 > > D-50668 K�ln > > Germany > > Tel.: +49 221 148 31277 > > Fax: +49 221 148 43963 > > Mobil: +49 179 59 064 59 > > e-Mail: Oliver.Lauer@axa.de > > _____________________________ > > > > > -----Urspr�ngliche Nachricht----- > Von: Tom Drake [mailto:rtd@pobox.com] > Gesendet: Mittwoch, 7. November 2001 18:02 > An: Tomcat Users List > Betreff: Re: Distributed Session Managment / Clusters > > > I read the source code. > > ----- Original Message ----- > From: "Lauer, Oliver" > To: "'Tomcat Users List'" ; "'Tom Drake'" > > Sent: Wednesday, November 07, 2001 8:25 AM > Subject: AW: Distributed Session Managment / Clusters > > > | Thanx, it helps but where did you found the information to do so ? > | > | > AXA eSolutions GmbH > | > AXA Konzern AG Germany > | > Oliver Lauer > | > Web Architect > | > W�rthstra�e 34 > | > D-50668 K�ln > | > Germany > | > Tel.: +49 221 148 31277 > | > Fax: +49 221 148 43963 > | > Mobil: +49 179 59 064 59 > | > e-Mail: Oliver.Lauer@axa.de > | > _____________________________ > | > > | > | > | -----Urspr�ngliche Nachricht----- > | Von: Tom Drake [mailto:rtd@pobox.com] > | Gesendet: Mittwoch, 7. November 2001 17:06 > | An: Tomcat Users List > | Betreff: Re: Distributed Session Managment / Clusters > | > | > | Oliver: > | > | I can't give you a definitive answer, because I haven't done it yet. > | However, If you look in the server.xml that comes with the tomcat > | binary distribution, you'll find an entry for PersistentManager under > | the /examples context. From what I can tell, you'll need to take these > | steps: > | - clone this into your context > | - change the name to DistributedManager > | - Add a Cluster definition inside the Engine definition > | > | I think the Cluster definition may need to look like this: > | > | | className="org.apache.cluster.StandardCluster" > | clusterName="The name of your cluster" > | checkInterval="interval in seconds to sleep between checking for data on > | the multicast socket" > | multicastPort="Port number to listen on" > | multicastAddress="inet address for multicast (See rfc3171)" > | > | /> > | > | This may not be correct, but I hope it is helpful. Let me know if you are > | successful > | > | ----- Original Message ----- > | From: "Lauer, Oliver" > | To: "'Tomcat Users List'" ; "'Tom Drake'" > | > | Sent: Wednesday, November 07, 2001 4:31 AM > | Subject: AW: Distributed Session Managment / Clusters > | > | > | | How did you configure Tomcat to do so ? I don't know the answer to your > | | question but I'm interested in how you've set up the TC cluster cause I > | | didn't find anything in the docs. > | | Thanx > | | Oliver > | | > | | > AXA eSolutions GmbH > | | > AXA Konzern AG Germany > | | > Oliver Lauer > | | > Web Architect > | | > W�rthstra�e 34 > | | > D-50668 K�ln > | | > Germany > | | > Tel.: +49 221 148 31277 > | | > Fax: +49 221 148 43963 > | | > Mobil: +49 179 59 064 59 > | | > e-Mail: Oliver.Lauer@axa.de > | | > _____________________________ > | | > > | | > | | > | | -----Urspr�ngliche Nachricht----- > | | Von: Tom Drake [mailto:rtd@pobox.com] > | | Gesendet: Dienstag, 6. November 2001 19:47 > | | An: Tomcat Users List > | | Betreff: Distributed Session Managment / Clusters > | | > | | > | | Can someone help me understand how the Distributed Session > | | Management works. From what I can tell, if you have a cluster > | | of Tomcat 4.x instances running, and you've configured each of > | | them to use the 'DistributedManager' for managing Session > | | data, then : > | | > | | - each time a new session is created, a copy is broadcast > | | (UDP/Multicast) to the the other Tomcat instances. > | | - When the other sessions receive the remote Session object > | | they append this object to a 'stack' (managed by a > | | ClusterReceiver object). > | | - The DistributedManager has it's own background thread that > | | periodically wakes up and moves any remote Session objects > | | from it's ClusterReceiver into its own list of Sessions. > | | > | | I cannot find any code that causes an updated Session to be broadcast > | | to the other Tomcat instances. Am I missing something? > | | > | | As an alternative, I could use the JDBC Session store mechanism to > | | persist Sessions to a database. In my case, the database is far to > | | heavyweight of a solution. I don't have the need for persistence other > | | than in a very transitory way, that is to say, that I need for each > Tomcat > | | instance to have an 'up-to-date' copy of the users Session. > | | > | | Regards, > | | > | | Tom Drake > | | > | | > | | -- > | | To unsubscribe: > | | For additional commands: > | | Troubles with the list: > | | > | | > | | ---------------------------- > | | Aus Rechts- und Sicherheitsgruenden ist die in dieser E-Mail gegebene > | Information nicht rechtsverbindlich. Eine rechtsverbindliche Bestaetigung > | reichen wir Ihnen gerne auf Anforderung in schriftlicher Form nach. > Beachten > | Sie bitte, dass jede Form der unautorisierten Nutzung, Veroeffentlichung, > | Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail nicht > gestattet > | ist.Diese Nachricht ist ausschliesslich fuer den bezeichneten Adressaten > | oder dessen Vertreter bestimmt. Sollten Sie nicht der vorgesehene Adressat > | dieser E-Mail oder dessen Vertreter sein, so bitten wir Sie, sich mit dem > | Absender der E-Mail in Verbindung zu setzen. > | | ---------------------------- > | | For legal and security reasons the information provided in this e-mail > is > | not legally binding. Upon request we would be pleased to provide you with > a > | legally binding confirmation in written form. Any form of unauthorised > use, > | publication, reproduction, copying or disclosure of the content of this > | e-mail is not permitted. This message is exclusively for the person > | addressed or their representative. If you are not the intended recipient > of > | this message and its contents, please notify the sender immediately. > | | --------------------------- > | | > | | > | | > | | > | > | > | > | -- > | To unsubscribe: > | For additional commands: > | Troubles with the list: > | > | > | ---------------------------- > | Aus Rechts- und Sicherheitsgruenden ist die in dieser E-Mail gegebene > Information nicht rechtsverbindlich. Eine rechtsverbindliche Bestaetigung > reichen wir Ihnen gerne auf Anforderung in schriftlicher Form nach. Beachten > Sie bitte, dass jede Form der unautorisierten Nutzung, Veroeffentlichung, > Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail nicht gestattet > ist.Diese Nachricht ist ausschliesslich fuer den bezeichneten Adressaten > oder dessen Vertreter bestimmt. Sollten Sie nicht der vorgesehene Adressat > dieser E-Mail oder dessen Vertreter sein, so bitten wir Sie, sich mit dem > Absender der E-Mail in Verbindung zu setzen. > | ---------------------------- > | For legal and security reasons the information provided in this e-mail is > not legally binding. Upon request we would be pleased to provide you with a > legally binding confirmation in written form. Any form of unauthorised use, > publication, reproduction, copying or disclosure of the content of this > e-mail is not permitted. This message is exclusively for the person > addressed or their representative. If you are not the intended recipient of > this message and its contents, please notify the sender immediately. > | --------------------------- > | > | > | > | > > > > -- > To unsubscribe: > For additional commands: > Troubles with the list: > > > ---------------------------- > Aus Rechts- und Sicherheitsgruenden ist die in dieser E-Mail gegebene Information nicht rechtsverbindlich. Eine rechtsverbindliche Bestaetigung reichen wir Ihnen gerne auf Anforderung in schriftlicher Form nach. Beachten Sie bitte, dass jede Form der unautorisierten Nutzung, Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail nicht gestattet ist.Diese Nachricht ist ausschliesslich fuer den bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein, so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu setzen. > ---------------------------- > For legal and security reasons the information provided in this e-mail is not legally binding. Upon request we would be pleased to provide you with a legally binding confirmation in written form. Any form of unauthorised use, publication, reproduction, copying or disclosure of the content of this e-mail is not permitted. This message is exclusively for the person addressed or their representative. If you are not the intended recipient of this message and its contents, please notify the sender immediately. > --------------------------- > > > > -- > To unsubscribe: > For additional commands: > Troubles with the list: > -- To unsubscribe: For additional commands: Troubles with the list: