On 12/12/2022 01:18, Tim N wrote:
From the official documentation
"The all-to-all replication is an algorithm that is only efficient when the
clusters are small. For larger clusters, you should use the BackupManager"
Any ideas on what the limit is or how to measure it? Any good articles?
It i
>From the official documentation
"The all-to-all replication is an algorithm that is only efficient when the
clusters are small. For larger clusters, you should use the BackupManager"
Any ideas on what the limit is or how to measure it? Any good articles?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Clemens,
On 7/25/17 9:54 AM, Clemens Eisserer wrote:
> Hi there,
>
> What is the strictest / most conservative setting for
> channelSendOptions when using SimpleTcpCluster for session
> replication (synchronous + ack + ??) ? I
Hi there,
What is the strictest / most conservative setting for
channelSendOptions when using SimpleTcpCluster for session replication
(synchronous + ack + ??) ?
I have a web-app where each request dependes on the session-state of
the previous one and unfortunatelyI have to deploy in an
Hi!
Thanks for your reply!
We have evaluated backupmanager and it does indeed seem to solve the issue!
br
/Linus
On 8 April 2015 at 12:30, Mark Thomas wrote:
> On 07/04/2015 21:46, Linus Brimstedt wrote:
> > Hello,
> >
> > We have a problem with SimpleTcpCluster an
On 07/04/2015 21:46, Linus Brimstedt wrote:
> Hello,
>
> We have a problem with SimpleTcpCluster and session replication.
> We have tested this in Tomcat 7 and 8 (latest versions) on Windows Server
> using latest revision of Hotspot JDK version 7, but checking the code it
> seem
Hello,
We have a problem with SimpleTcpCluster and session replication.
We have tested this in Tomcat 7 and 8 (latest versions) on Windows Server
using latest revision of Hotspot JDK version 7, but checking the code it
seems like this is not covered anyway.
The problem:
Replication works well
Hi,
On Tue, Nov 20, 2012 at 2:03 PM, Stephen Nelson-Smith
wrote:
> Hi Daniel.
>
> On Tue, Nov 20, 2012 at 1:55 PM, Daniel Mikusa wrote:
>> On Nov 20, 2012, at 5:53 AM, Stephen Nelson-Smith wrote:
>> I've encountered this with Tomcat clustering on CentOS in the past.
>> Tomcat's default configu
Hi Daniel.
On Tue, Nov 20, 2012 at 1:55 PM, Daniel Mikusa wrote:
> On Nov 20, 2012, at 5:53 AM, Stephen Nelson-Smith wrote:
> I've encountered this with Tomcat clustering on CentOS in the past. Tomcat's
> default configuration for the cluster receiver will automatically look up the
> address t
On Nov 20, 2012, at 5:53 AM, Stephen Nelson-Smith wrote:
> Hi,
>
> I'm trying to test simple session sharing using SimpleTCPCluster on
> Tomcat 7.0.32.
>
> Following the documentation, I've uncommented the className="org.apache.catalina.ha.tcp.SimpleTcpCluster
Hi,
I'm trying to test simple session sharing using SimpleTCPCluster on
Tomcat 7.0.32.
Following the documentation, I've uncommented the element, and
ensured is in the web.xml of the examples web app.
>From the docs:
- All your session attributes must implement java.io.Seriali
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
|> In fact, you still are not covered, because removing the object from the
|> session merely removes the reference. If the session replicator is
|> running and copying, say, a Map to another machine in the clust
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
| no, its just common sense, given that the session should represent a
| client state,
| and by the time the cluster tries to serialize it, the request is over.
There's no guarantee t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
| no, its just common sense, given that the session should represent a
| client state,
| and by the time the cluster tries to serialize it, the request is over.
There's no guarantee that the request is complete
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
| if you look at the stack trace, there is no error in the clustering
| code. something is modifying your session attribute while the
cluster is
| trying to send it
I'm suggesting t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
| if you look at the stack trace, there is no error in the clustering
| code. something is modifying your session attribute while the cluster is
| trying to send it
I'm suggesting that this should not be conside
if you look at the stack trace, there is no error in the clustering
code. something is modifying your session attribute while the cluster is
trying to send it
Filip
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
| the solution
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
| the solution is to not store stuff in the session modified by other
| threads, if that's the case, then its not really something you wanna
| store in a session
What's wrong with modifying something in a sessio
the solution is to not store stuff in the session modified by other
threads, if that's the case, then its not really something you wanna
store in a session
Filip
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
| this is not a cl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
| this is not a cluster error, basically, you are storing a map in the
| session, and someone is modifying the map while the cluster is trying to
| replicate it
How should this be solved? The OP could really onl
this is not a cluster error, basically, you are storing a map in the
session, and someone is modifying the map while the cluster is trying to
replicate it
org.apache.commons.collections.LRUMap
Filip
LERBSCHER JEAN-PIERRE wrote:
Hi,
We work on Tomcat clustered server (5.5) and we have thi
Hi,
We work on Tomcat clustered server (5.5) and we have this exception in the log
(at 5-10 TPS).
Could you explain us what's hapenning. Have you a solution? Thanks.
Exception:
SEVERE: Failed to serialize the session!
java.util.ConcurrentModificationException
at
org.apac
Are you saying that the message below keeps repeating itself? over and
over again?
what does your full log say?
Filip
Jean-frederic Clere wrote:
Hi,
I have trying to get the SimpleTcpCluster running but I only get:
+++
INFO: Replication member
Hey,
I think you must used a new Tomcat version. In last year I change a lot. Use
tomcat 5.5.12 for your configuration and read the docs for configruation
options:
http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html
My perferred mode for production is fastasyncqueue!
Regards
Peter
mic
-- Forwarded message --
From: michelle wang <[EMAIL PROTECTED]>
Date: Oct 24, 2005 8:49 PM
Subject: Please Help!!! No session state received, time out 60s during
tomcat start up
To: users@tomcat.apache.org
I'm running 2 tomcat (5.0.18) instances with Simple TCP Clustering on the
sa
25 matches
Mail list logo
