Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (herse.apache.org: domain of Andy.Scherzinger@sdm.de
 designates 192.76.162.229 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: AW: AW: Tomcat 5.5 Cluster: Session Replication before sending
 the response
Date: Wed, 17 Jan 2007 10:38:52 +0100
Message-ID: <75B38C0577898E48A3FD2C972857A57CE3E12B@ffmmail1.sdm.de>
In-Reply-To: <919BD087-09EC-4C5E-8DB8-9C2CB00E64D6@objektpark.de>
Thread-Topic: AW: AW: Tomcat 5.5 Cluster: Session Replication before sending
 the response
Thread-Index: Acc6E5m+h3bIWRvaTk6Cry+sVfvSsAABvmJQ
From: <Andy.Scherzinger@sdm.de>
To: <users@tomcat.apache.org>

Hi Peter,

Thanks for your answer. As far as I know the SimpleTcpReplicationManager =
has been implemented for Tomcat 4 an replicates the session when it =
changes. So everytime the session changes it would replicate it. Thus TC =
would replicate my session several times during the processing of a =
request which would not be appropriate since the session would hold the =
wrong information in case tomcat crashes during the processing of a =
request but already replicated the session several times. Thus it really =
looks like the only way to replicate the complete session is to =
implement a filter or valve.

Regards
Andy

-----Urspr=FCngliche Nachricht-----
Von: Peter Rossbach [mailto:pr@objektpark.de]=20
Gesendet: Mittwoch, 17. Januar 2007 09:43
An: Tomcat Users List
Betreff: Re: AW: AW: Tomcat 5.5 Cluster: Session Replication before =
sending the response

Hi

you can give o.a.c.cluster.session.SimpleTcpReplicationManager a chance, =
but I don't know it works really.

Regards
Peter


Am 16.01.2007 um 15:57 schrieb <Andy.Scherzinger@sdm.de>
<Andy.Scherzinger@sdm.de>:

> Hi Filip,
>
> I understand that I will just change the session in a way the delta=20
> manager will replicate everything.
> But is there no other Manager I can use which just replicates the=20
> complete session and not just the changed data (like the DeltaManager=20
> does)?!
>
> I couldn't find a Manager which replicates everything. Is there one?
>
> Thanks in advance!
>
> Andy
>
>
> -----Urspr=FCngliche Nachricht-----
> Von: Filip Hanik - Dev Lists [mailto:devlists@hanik.com]
> Gesendet: Dienstag, 16. Januar 2007 15:35
> An: Tomcat Users List
> Betreff: Re: AW: Tomcat 5.5 Cluster: Session Replication before=20
> sending the response
>
> even with this method, you are not managing the sessions, you're just=20
> making sure that everything gets replicated, so doing this, you are=20
> not changing the session manager.
> remember, the code below would be inserted into a filter or a valve
>
> Filip
>
> wrote:
>> Hi Filip,
>>
>> Thanks for your answer. I also thought about this solution of just=20
>> setting all objects again at the end of the doGet method.
>> But if possible I would like to use a tomcat replication mechanism=20
>> since I do not want to "manage" session since I have a tomcat-=20
>> built-in session manager :)
>>
>> Andy
>>
>> -----Urspr=FCngliche Nachricht-----
>> Von: Filip Hanik - Dev Lists [mailto:devlists@hanik.com]
>> Gesendet: Mittwoch, 10. Januar 2007 16:52
>> An: Tomcat Users List
>> Betreff: Re: Tomcat 5.5 Cluster: Session Replication before sending=20
>> the response
>>
>> to achieve what you want, although slower, you can create a filter,=20
>> and in that filter simply set all the attributes again
>>
>> Enumeration e =3D session.getAttributeNames(); while ( e.hasNext() ) =
{
>>   String name =3D e.next();
>>   Object value =3D session.getAttribute(name);
>>   if ( value !=3D null ) session.setAttribute(name,value); }
>>
>> you get the point :)
>>
>> Filip
>>
>> wrote:
>>
>>> Hi everybody,
>>>
>>> I have a Tomcat 5.5 cluster with 2 nodes on SLES8 and want to=20
>>> replicate the complete session before the response is send.
>>> According to the Tomcat Clustering documentation the example with=20
>>> the DeltaManager does this since the ReplicationValve triggers the=20
>>> replication after the request has been processed and before the=20
>>> response is sent.
>>>
>>> Unfortunately the DeltaManager only replicates the changed data. =20
>>> Only changes made by using methods like setAttribute make changes=20
>>> visible to the DeltaManager and changes made to the object (like=20
>>> changing one field value noch setAttribute-call) do not.
>>> Thus I would need to change the way these objects are handled in the =

>>> application. So I thought it would be the easiest way to just=20
>>> replicate the complete session instead of changes only. Is this=20
>>> possible?
>>>
>>> JavaDoc of org.apache.catalina.session.StandardManager:
>>> "Standard implementation of the Manager interface that provides=20
>>> simple session persistence across restarts of this component (such=20
>>> as when the entire server is shut down and restarted, or when a=20
>>> particular web application is reloaded."
>>>
>>> This sounds like the session is only replicated when the server ist=20
>>> shutdown/restarted/app reloaded. It also doesn't specify what is=20
>>> replicated - the complete session?
>>>
>>> Any suggestions?
>>>
>>> Thanks in advance
>>> --Andy
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,=20
> e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,=20
> e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, =
e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org