Ok I'm going to share some ideas I've been mulling on this topic
since it's been coming up a lot lately. Other people seem to be
interested in having Tomcat natively do load balancing itself, by
redirecting requests between instances in a server farm. What
I'm actually more interested in getting
[EMAIL PROTECTED] typed the following on 11:16 PM 12/24/2000 +0200
>I'm planning to implement session replication (for tomcat 3.3) in the
>following steps:
Sounds like we should combine efforts, hopefully we can share as much
code as possible across both 3.3 and 4.0. My understanding is that the
costin 00/12/24 20:46:50
Removed: src/webdav/org/apache/tomcat/webdav DefaultServlet.java
LocalStrings.properties WebdavServlet.java
src/webdav/org/apache/tomcat/webdav/resources
DirectoryBean.java FileResources.java
costin 00/12/24 20:43:15
Modified:.build.xml
Log:
Removed any reference to other facades - non-servlet22 facades will not
be part of the standard distribution.
Removed webdav - it was a new feature for 3.3, and no new features should
be part of 3.3. The code will b
You are right , the code Jon points it's at 3.2 inside
org.apache.tomcat.Session.writeobject, i think, but i just overlooked
the code, i'm now trying to find myself, not only the code :-).
Saludos ,
Ignacio J. Ortega
> -Mensaje original-
> De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED
Hi,
I'm not sure about that.
Jon wants to override session's read/write object. He has the right code in
jserv to do that. The code you are pointing to still use default
read/writeobject for session which is exactly what I did.
M I right?
This is the right read/write object by Jon (I just porte
on 12/24/2000 3:58 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Ahh...
>
> The patches I have sent were written originally to 3.2.
> Jon's code was part of 3.2 (and I have used it) but is not included in 3.3.
>
> Thanks to Jon having my attention to that. I'll fix that soon.
>
> --Shai
Hola Shai:
for 3.3, The code Jon points it's at
org.apache.tomcat.util.ObjectSerializer and it's only used inside
org.apache.tomcat.modules.session.SimpleSessionStore, reload hook.
Saludos ,
Ignacio J. Ortega
> -Mensaje original-
> De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> En
Ahh...
The patches I have sent were written originally to 3.2.
Jon's code was part of 3.2 (and I have used it) but is not included in 3.3.
Thanks to Jon having my attention to that. I'll fix that soon.
--Shai
-Original Message-
From: Jon Stevens [mailto:[EMAIL PROTECTED]]
Sent: Monday,
Jon,
I believe that you want people to contribute to this project,
but comments like the ones you made in this thread are more
likely to scare people away. I'm afraid many would-be
contributors read these mails and think "if this is the way
my contributions will be received, I'm out of here".
on 12/24/2000 3:31 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Where is the piece of code you have written for jserv???
>
> --Shai
Now that is a really funny question. Think about it for a second.
-jon
Where is the piece of code you have written for jserv???
--Shai
-Original Message-
From: Jon Stevens [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 25, 2000 00:47
To: [EMAIL PROTECTED]
Subject: Re: [PATCH] Tomcat session replicator - Pathces for phase I
on 12/24/2000 1:26 PM, "[EMAIL
on 12/24/2000 1:26 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> try {
> + fStream = new FileOutputStream(f);
> + oStream = new ObjectOutputStream(fStream);
> + // Serialize to file all active session
> + Enumeration ids = sessions.keys();
> + ServerSession session = null;
> +
on 12/24/2000 1:26 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> + while (ids.hasMoreElements()) {
> +session =
> findSession(ids.nextElement().toString());
> +if (!session.getTimeStamp().isValid())
> + continue;
> +oStream.writeObject(session);
> + }
> + oStream.fl
on 12/24/2000 1:26 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> + try {
> + fStream = new FileOutputStream(f);
> + oStream = new ObjectOutputStream(fStream);
> + // Serialize to file all active session
> + Enumeration ids = sessions.keys();
> + ServerSession session = null;
> +
on 12/24/2000 1:16 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> 2. Let Tomcat send session information (for every request) to all other
> tomcat in a cluster. This will let apache (using mod_jk) to forward requests
> to other tomcats after finding out that the original tomcat (by jvmRoute
Again, with patches as attachment.
--Shai
-Original Message-
From: Shai Fultheim (BRM IL)
Sent: Sunday, December 24, 2000 23:27
To: [EMAIL PROTECTED]
Subject: [PATCH] Tomcat session replicator - Pathces for phase I
Hi,
These patches will allow you to add serialize="true" to you conte
Hi,
These patches will allow you to add serialize="true" to you context and
having your context saved to disk.
Index: src/share/org/apache/tomcat/core/Context.java
===
RCS file:
/home/cvspublic/jakarta-tomcat/src/share/org/apache/t
HI,
Totally agree.
I'm planning to implement session replication (for tomcat 3.3) in the
following steps:
1. Having persistent session store. Letting tomcat store its session
information to file and read it while coming up. Saving session will happen
as soon as request will be finished. - This
Ok I'm going to share some ideas I've been mulling on this topic
since it's been coming up a lot lately. Other people seem to be
interested in having Tomcat natively do load balancing itself, by
redirecting requests between instances in a server farm. What
I'm actually more interested in getting
[EMAIL PROTECTED] typed the following on 10:35 AM 12/22/2000 +0200
...
>Mod_jk on each machine forward requests based on sessionID to the right
>tomcat (this is my patch to 3.2b7).
...
>THE NEW IDEA is, assuming all of what I have stated above is working. We can
>take apache out of the picture.
>H
Hi,
You don't seem to be posting built versions of mod_jk.so for linux anymore.
I could do with this. Could somebody EMail it to me or tell me where I could
get it.
I'm not currently subscribed to the list so please send to
[EMAIL PROTECTED]
Thanks.
Dave
22 matches
Mail list logo