as well. I'll take a
look. . . .
Aaron
> -Original Message-
> From: Filip Hanik [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 15, 2002 9:12 PM
> To: Tomcat Developers List
> Subject: Re: Tomcat: Distributed Session Management revisited
>
> hi, let me intr
hi, let me introduce myself.
My name is Filip Hanik and I just rejoined this mailing list since my time
has freed up a little bit lately.
I was looking through the source code and the archives and was wondering
what the status Tomcat has on session replication.
When looking through the source cod
FYI.
- Original Message -
From: "Tom Drake" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Cc: "Tomcat Dev List" <[EMAIL PROTECTED]>
Sent: Sunday, December 16, 2001 8:01 AM
Subject: Re: tom4 session and loadbalancing / Di
Michael:
As it happens, I am currently working on a solution to this problem.
Look for messages in the archive with 'Distributed Session
Management' in the subject.
In a nutshell, all tomcat instances in a 'cluster' will be able to share
session data.
I've already co
List" <[EMAIL PROTECTED]>; "Tom Drake"
<[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 11:41 AM
Subject: Re: Tomcat: Distributed Session Management revisited
|
|
| On Tue, 13 Nov 2001, Tom Drake wrote:
|
| > I want a distributed session store, where all sessions
>> Costin,
>>
>> that point of view is really interesting. What about separating the
>> distribution part from the integration part of a integrated solution.
>> That would user's give the option to use the "transparent session
>> replication" or to use "explicit object replication services".
>> Th
s List <[EMAIL PROTECTED]>
> > Subject: Re: Distributed Session Management
> >
> > The only problem with including the tests right in the same package
> > is that they can be hard to remove for a test-free distribution. Also,
> > since they are in the same pack
- Original Message -
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Thursday, November 15, 2001 11:39 AM
Subject: Re: Distributed Session Management
|
|
| On Thu, 15 Nov 2001, Paul Speed wrote:
|
On Thu, 15 Nov 2001, Paul Speed wrote:
> Date: Thu, 15 Nov 2001 14:40:35 -0500
> From: Paul Speed <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: Tomcat Developers List <[EMAIL PROTECTED]>
> Subject: Re: Distributed Session Man
ind. :)
-Paul
Tom Drake wrote:
>
> Mika:
>
> - Original Message -
> From: "Mika Goeckel" <[EMAIL PROTECTED]>
> To: "Tomcat Developers List" <[EMAIL PROTECTED]>; "Tom Drake"
> <[EMAIL PROTECTED]>
> Sent: Thursday, Novembe
Mika:
- Original Message -
From: "Mika Goeckel" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>; "Tom Drake"
<[EMAIL PROTECTED]>
Sent: Thursday, November 15, 2001 3:31 AM
Subject: Re: Distributed Session Management
|
seum on this list).
Tom
- Original Message -
From: "Mika Goeckel" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Thursday, November 15, 2001 3:24 AM
Subject: Re: Tomcat: Distributed Session Management revisited
| Costin,
|
| that p
On Thu, 15 Nov 2001, Mika Goeckel wrote:
> Costin,
>
> that point of view is really interesting. What about separating the
> distribution part from the integration part of a integrated solution.
> That would user's give the option to use the "transparent session
> replication" or to use "explicit
59
> e-Mail: [EMAIL PROTECTED]
> _
>
-Ursprüngliche Nachricht-
Von: Mika Goeckel [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 15. November 2001 12:32
An: Tomcat Developers List; Tom Drake
Betreff: Re: Distributed Session Management
Tom,
from my (personal?!) philosophy, test
responsibility
cards?
M.
- Original Message -
From: "Tom Drake" <[EMAIL PROTECTED]>
To: "Tomcat Dev List" <[EMAIL PROTECTED]>
Sent: Wednesday, November 14, 2001 8:39 PM
Subject: Distributed Session Management
> Tomcat Developers:
>
> I&#x
, November 14, 2001 6:27 PM
Subject: Re: Tomcat: Distributed Session Management revisited
> To clarify: creating a Distributed Session Manager is a good idea, and
> something that would be great for users.
>
> My problem is with designing it at container-level, as an implementation
> o
Tomcat Developers:
I'm going to try to synthesize the results of yesterdays
discussion on Distributed Session Management into some
working code. From what I can tell, there will be some
changes and new objects in the org.apache.session
package, and possibly some new objects i
To clarify: creating a Distributed Session Manager is a good idea, and
something that would be great for users.
My problem is with designing it at container-level, as an implementation
of the servlet session API.
Having all objects in a session distributed and no control or feedback is
not good.
[EMAIL PROTECTED] wrote:
>
> On Tue, 13 Nov 2001, Paul Speed wrote:
>
> > I think the idea is that you'd byte compare on "commit" which ideally
> > would happen at request boundaries. So in this case a single request
> > becomes a "transaction"... which indeed opens up its own issues, but
> > n
November 2001 11:26
An: Tomcat Developers List
Betreff: Re: Tomcat: Distributed Session Management revisited
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, November 14, 2001 12:26 AM
Subject: Re: Tomcat: Dis
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, November 14, 2001 12:26 AM
Subject: Re: Tomcat: Distributed Session Management revisited
> On Tue, 13 Nov 2001, Mika Goeckel wrote:
>
> >
On Tue, 13 Nov 2001, Paul Speed wrote:
> I think the idea is that you'd byte compare on "commit" which ideally
> would happen at request boundaries. So in this case a single request
> becomes a "transaction"... which indeed opens up its own issues, but
> no bigger than the ones that were always
See below
- Original Message -
From: "Paul Speed" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 3:48 PM
Subject: Re: Tomcat: Distributed Session Management revisited
... stuff deleted ...
|
| Th
[EMAIL PROTECTED] wrote:
>
> On Tue, 13 Nov 2001, Mika Goeckel wrote:
>
> > I completely agree, that the API lacks proactive support for things in the
> > background that may fail.
> > But given the fact, that we support a reference implementation which has
> > managed to provide really profes
Mika Goeckel wrote:
>
[ snip ]
> >
> > I'm not saying this is necessarily a "good" idea, but you can byte
> > compare the resulting session serialization to see if the session
> > objects have changed. All you have to do is keep a local copy of
> > the original session during the request. Not
On Tue, 13 Nov 2001, Mika Goeckel wrote:
> I completely agree, that the API lacks proactive support for things in the
> background that may fail.
> But given the fact, that we support a reference implementation which has
> managed to provide really professional services to users (other ref
> impl
- Original Message -
From: "Paul Speed" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 11:30 PM
Subject: Re: Tomcat: Distributed Session Management revisited
>
>
> Tom Drake wrote:
>
Tom Drake wrote:
>
> - Original Message -
> From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> To: "Tomcat Developers List" <[EMAIL PROTECTED]>; "Tom Drake"
> <[EMAIL PROTECTED]>
> Sent: Tuesday, November 13, 2001 1:25
See my comments below.
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>; "Tom Drake"
<[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 2:08 PM
Subject: Re: Tomcat: Distributed Session Management
- Original Message -
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>; "Tom Drake"
<[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 1:25 PM
Subject: Re: Tomcat: Distributed Session Manag
On Tue, 13 Nov 2001, Tom Drake wrote:
> | One question - wouldn't be better if the 'distributed session management'
> | would be first designed and discussed _outside_ of the ServletSession
> | context ?
>
> I agree.
>
> | Designing the SessionManager as a s
<[EMAIL PROTECTED]>
> Subject: Re: Tomcat: Distributed Session Management revisited
>
>
> - Original Message -
> From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> To: "Tomcat Developers List" <[EMAIL PROTECTED]>
> Sent: Tuesday
>
> Subject: Re: Tomcat: Distributed Session Management revisited
>
>
> - Original Message -
> From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> To: "Tomcat Developers List" <[EMAIL PROTECTED]>; "Tom Drake"
> <[EMAIL PROT
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Cc: "Tom Drake" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 1:05 PM
Subject: Re: Tomcat: Distributed Session Management revisited
|
| On
- Original Message -
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 12:31 PM
Subject: Re: Tomcat: Distributed Session Management revisited
|
|
| On Tue, 13 Nov 2001, Mik
- Original Message -
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>; "Tom Drake"
<[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 11:41 AM
Subject: Re: Tomcat: Distributed Session
See below.
- Original Message -
From: "Pier Fumagalli" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 12:23 PM
Subject: Re: Tomcat: Distributed Session Management revisited
| > ASFAICT, minimal
One question - wouldn't be better if the 'distributed session management'
would be first designed and discussed _outside_ of the ServletSession
context ?
In other words, a SessionManager that would store and provide
fail-over, etc for serializable objects. It can have a
sage -
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 9:31 PM
Subject: Re: Tomcat: Distributed Session Management revisited
>
>
> On Tue, 13 Nov 2001, Mika Goeckel wrote:
&g
On Tue, 13 Nov 2001, Pier Fumagalli wrote:
>
> So, basically, we have to design a lock/unlock mechanism (that complicates
> stuff). It would be easier to achieve without that requirement... (god knows
> why Danny added it).
>
See the answer I just sent for more details -- not enforcing this
re
On Tue, 13 Nov 2001, Mika Goeckel wrote:
> Date: Tue, 13 Nov 2001 21:19:35 +0100
> From: Mika Goeckel <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: Tomcat Developers List <[EMAIL PROTECTED]>
> Subject: Re: Tomcat: Distrib
> Can't help you on that... But, if we "customize" the lookup tables
> abstracting it from JNDI, we could write also some C code for the
web-server
> modules that could participate in our session pooling group, and direct
> requests where they should be, two pigeons with a single shot :)
Somethi
On 13/11/2001 07:59 pm, "Mika Goeckel" <[EMAIL PROTECTED]> wrote:
> Scenario:
>
> 4) 10 Tomcat webservers acting as SessionManagers for Sessions initially
> created by themselves or being assigned responsibility afterwards for a
> specific session.
> In this scenario every Tomcat backs up sessio
On 13/11/2001 07:41 pm, "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 13 Nov 2001, Tom Drake wrote:
>
>> I want a distributed session store, where all sessions are known (or
>> are knowable) by all members of the cluster, with a built-in
>> fail-over mechanism?
>
> As you guy
On 13/11/2001 06:53 pm, "Tom Drake" <[EMAIL PROTECTED]> wrote:
> | > SNMP, ah ja. I've got no knowledge at all 'bout that, so fight with some
> | > other lobbyists :-)
> |
> | Same here...
>
> Didn't mean to take a left turn. Sorry I mentioned it.
Oh, I mean, I don't mind... The only thing is t
; <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>; "Tom Drake"
<[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 8:41 PM
Subject: Re: Tomcat: Distributed Session Management revisited
>
>
> On Tue, 13 Nov 2001, Tom Drake wrote:
&g
:-)
> | On 13/11/2001 04:38 pm, "Mika Goeckel" <[EMAIL PROTECTED]> wrote:
> |
> | > SNMP, ah ja. I've got no knowledge at all 'bout that, so fight with
some
> | > other lobbyists :-)
> |
> | Same here...
>
> Didn't mean to take a left turn. Sorry I mentioned it.
No need to mention, nobody felt
On Tue, 13 Nov 2001, Tom Drake wrote:
> I want a distributed session store, where all sessions are known (or
> are knowable) by all members of the cluster, with a built-in
> fail-over mechanism?
As you guys discuss this, don't forget a very important requirement in the
servlet specification wi
- Original Message -
From: "GOMEZ Henri" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 9:15 AM
Subject: RE: Tomcat: Distributed Session Management revisited
... stuff deleted ...
| >Notice also,
- Original Message -
From: "Pier Fumagalli" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 8:56 AM
Subject: Re: Tomcat: Distributed Session Management revisited
| On 13/11/2001 04:38 pm, "Mi
>Pier:
>
>Great discussion points. I really appreciate your thoughtful feedback.
>
>My comment about Tomcat caching session data does not preclude
>it from being stored in the remote session server. Indeed, this would
>be required. My thought was this, in a multi-node network if multiple
>contiguo
Hi,
Interesting discussion, it's good to see some on this distribution
issue, the devils always in the detail! See comments
> | > But how would they know where the sessions ended up
>
> All session managers keep a copy of all sessions. So, it doesn't matter
> which server a client talks to
On 13/11/2001 04:38 pm, "Mika Goeckel" <[EMAIL PROTECTED]> wrote:
> SNMP, ah ja. I've got no knowledge at all 'bout that, so fight with some
> other lobbyists :-)
Same here...
> SessionManager/ServletContainer dualism:
> If we don't create a separate SessionManager residing in it's own JVM,
link with.
Mika
- Original Message -
From: "Tom Drake" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 4:47 PM
Subject: Re: Tomcat: Distributed Session Management revisited
> Pier, Mikal:
>
> I
Pier, Mikal:
I agree, I think the juices are flowing. See below
Tom
- Original Message -
From: "Mika Goeckel" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 1:37 AM
Subject: Re: Tomcat: Distribu
throws RemoteException;
public void
removeSessionAttribute(String sessionId, String attributeName, byte
[] value)
throws RemoteException;
- Original Message -
From: "Pier Fumagalli" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <
Pier, Tom,
cool, the discussion is starting to become interesting. :-)
comments below:
- Original Message -
From: "Pier Fumagalli" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 3:04 AM
Subject:
On 13/11/2001 12:54 am, "Tom Drake" <[EMAIL PROTECTED]> wrote:
> Mika:
>
> Thanks for the reply. Here's some more thoughts on this subject.
>
> The primary problem that I see with the collaborative method
> (e.g. extending the multicast solution) is
> that all sessions will have to be sent to a
On 12/11/2001 11:14 pm, "Mika Goeckel" <[EMAIL PROTECTED]> wrote:
> I would vote for the cooperative approach, but I'd like to add some
> thoughts:
>
> Besides the primary session manager, there needs to be a backup session
> manager that captures the changes of sessions as well and is the crown
mplete failure of the remote session manager.
Tom
- Original Message -
From: "Pier Fumagalli" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 4:28 PM
Subject: Re: Tomcat: Distributed Session Mana
It's up to the web-application to replace
these values into
the Session if their contents change. This is enough for us to be able to
track which attributes
have actually changed.
Tom
- Original Message -
From: "Mika Goeckel" <[EMAIL PROTECTED]>
To: "Tomcat
ust yet, so I thought I'd throw this out to the whole dev
> list.
This is always the wiser choice...
> The current implementation is broken. The following message explains
> why and describes some possible solutions to this problem.
>
> This feature (e.g. distributed se
t: Monday, November 12, 2001 11:19 PM
Subject: Fw: Tomcat: Distributed Session Management revisited
> Tomcat Developers:
>
> This is a forward of a message that I sent to Bip and Craig a few days
ago,
> regarding distributed session managment (aka Clustering). I haven't gotten
>
roken. The following message explains
why and describes some possible solutions to this problem.
This feature (e.g. distributed session management) is an absolute
requirement
for any deployment that needs to scale beyond a single Tomcat instance, and
does not want the overhead of depending on JDBC f
Read the archives of this list...this comes up every few months, people talk
about it and then nothing happens...
This isn't a 100% easy problem to solve.
-jon
thanks a lot for the response. i've looked at the SessionINterceptor
but i can't see how it exposes enough functionality to implement
this paradigm. It seems more for messing with an existing session
as opposed to instantiating and returning one. Maybe I am
wrong though.
topher
> As far as where
a" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 05, 2001 4:45 PM
Subject: distributed session management
>
> Hi everybody. I hope this is the appropriate forum for this question.
> Currently I am doing distributed session management with a hacked up
&
Hi everybody. I hope this is the appropriate forum for this question.
Currently I am doing distributed session management with a hacked up
jserv that can persist serialized sessions in the DB if they are deemed
"dirty".
The session id encodes information regarding, among other thi
68 matches
Mail list logo
