DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-10-04 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540





--- Additional Comments From [EMAIL PROTECTED]  2005-10-04 14:13 ---
(In reply to comment #12)
 The differenc between 5.5.9 and 5.5.11 is that waitForAck is on default false
 for all sender modes. 
 Can you check with this config:
snip

The waitForAck was my problem indeed. Thanks you very much for pointing out. 

But now I'm a bit confused about the difference between pooled and
fastasyncqueue cluster replication really is. The docs state synchronous
replication guarantees the session to be replicated before the request returns.
But obviousely waitForAck is the controlling setting. Isn't it best to just
ignore the waitForAck setting and have it set false for fastasyncqueue and true
for pooled? 

The docs also state that Asynchronous replication, should be used if you have
sticky sessions until fail over, which implies that pooled should be used else.
But as this bug report turned out, sticky sessions are mandatory for correct
clustering. Maybe you should change the docs accordingly (This should go into
another bug report imo, but my bug 36542 was resolved as duplicate)

Thanks, 
Christoph



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-10-04 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540





--- Additional Comments From [EMAIL PROTECTED]  2005-10-04 21:01 ---
synchronous: send each session change to other cluster members before returning
response to client.

asychronous: same as synchronous, but use mutiple sender connections (use any
one, that is not currently busy).

fastasync: put session change message into local queue and then return response
to client. A seperate thread waits for messages coming into the queue and then
send the messages to the other cluster members.

waitforack: when ending the message, wait for an ACK type answering message from
the other cluster members before proceeding (make sending the messages more
reliable).

If one needs exact synchronization: synchronous are pooled mode with waitforack.
Application gets into trouble, when replication gets stuck.

If one can live with some latency between changes on the primary node and their
replication to the other nodes and on the other hand the cluster should
influence application performance and stability only very little: use session
stickyness in load balancers combined with fastasync and no waitforack.

synchronous/pooled without waitforack: lower latency for replication, although
synchronization is not exact.

fastasync with waitforack: decoupling replication from request/response but
ensuring that replication is checked for success.

You are right, we should make the docs more precise. The features are yet very
new and as usual documentation takes a while.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-30 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEEDINFO|NEW




--- Additional Comments From [EMAIL PROTECTED]  2005-09-30 23:56 ---
I would argue the ackTimeout=15000 should be an indicator that wait for ack 
=true,
do you really need two flags to say the same thing?
To simplify the implementation, I would use the following logic, and remove the
waitForAck flag all together.

ackTimeout  0 - wait for ack true, and time out set
ackTimeout = 0 - wait for ack false
ackTimeout = -1 - wait for ack true, no timeout

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-23 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|ASSIGNED|NEEDINFO




--- Additional Comments From [EMAIL PROTECTED]  2005-09-23 17:37 ---
The differenc between 5.5.9 and 5.5.11 is that waitForAck is on default false
for all sender modes. 
Can you check with this config:
Sender

className=org.apache.catalina.cluster.tcp.ReplicationTransmitter
replicationMode=pooled
waitForAck=true
doTransmitterProcessingStats=true
doProcessingStats=true
doWaitAckStats=true
ackTimeout=15000/

thanks
Peter

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEEDINFO|ASSIGNED




--- Additional Comments From [EMAIL PROTECTED]  2005-09-21 13:42 ---
Its been a while since I ran my test cases, but I will do it again

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540





--- Additional Comments From [EMAIL PROTECTED]  2005-09-20 19:36 ---
(In reply to comment #9)
 Christoph, if the scenario that you have is a single client thread per 
 session,
 then let us know, otherwise we will close this bug.

My Test Case above is actually quite simple. A single JMeter thread runs
subsequent requests on a cluster of 2 Tomcat servers. A jk load balancer without
sticky sessions (for testing only) does the distribution. The jsp page just
stores the hostname of the tomcat server in the session. No fancy
multi-threading or anything. TC 5.5.9 handles the situation correctly and
replicates the session before finishing the http request. 5.5.11 does not. So
pooled replication in definitely broken.

Please either fix it or document that it's broken. If you should choose not to
fix it, pooled, synchronous and asynchronous replication modes are basically
useless and should be removed. 

Thanks for pointing out that the servlet specs (SRV.7.7.2) state that Within an
application marked as distributable, all requests that are part of a session
must be handled by one Java Virtual Machine1 ( JVM ) at a time.  But in my
opinion that means that when the requests are finished, the session state should
already be replicated on all other cluster members. A Session with a single 7
char String object seems to need about 20 ms to replicate in my setup. Busy
servers with large Sessions may get into some hundreds of ms and this is a
problem for me.

Bye,
Christoph

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-19 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |




--- Additional Comments From [EMAIL PROTECTED]  2005-09-19 23:57 ---
I don't agree with that at all, sticky sessions is a great benefit, but pooled
synchronized cluster should be working.

at least it was in the good ol' days :)

Peter, do you know what changed in the cluster fix pack that made the synch
not work properly anymore?

Filip

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-19 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540





--- Additional Comments From [EMAIL PROTECTED]  2005-09-20 00:11 ---
(In reply to comment #6)
 I don't agree with that at all, sticky sessions is a great benefit, but pooled
 synchronized cluster should be working.
 
 at least it was in the good ol' days :)

No, it never was: the request might be complete from a HTTP standpoint while the
servlet is still running (= the client might send the next request, while the
replication hasn't been done yet). Besides, the spec requires that all
concurrent requests which belong to the same session be processed by the same 
host.

Non sticky sessions is broken for many cases, period. I'll let you close this as
INVALID again.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-19 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|NEEDINFO




--- Additional Comments From [EMAIL PROTECTED]  2005-09-20 00:26 ---
No, it never was: the request might be complete from a HTTP standpoint while 
the
servlet is still running (= the client might send the next request, while the
replication hasn't been done yet).

yes, this scenario has never been supported. that is correct.
But single thread client synchronization has always worked.

Christoph, if the scenario that you have is a single client thread per session,
then let us know, otherwise we will close this bug.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-19 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540





--- Additional Comments From [EMAIL PROTECTED]  2005-09-20 00:35 ---
(In reply to comment #8)
 yes, this scenario has never been supported. that is correct.
 But single thread client synchronization has always worked.

Yes, many webapps would work very well with this mode, while some others would 
not.

For this situation, taking several ms to replicate doesn't seem particularly
broken to me, although I suppose the 5.5.10 changelog is quite long.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2005-09-18 10:36 ---
As Remy tell you, sticky session is mandatory that
tomcat clustering works. Clustering is a fallback mechanism.

Peter

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-09 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |




--- Additional Comments From [EMAIL PROTECTED]  2005-09-09 10:48 ---
I did some further testing, and my test case works as expected with tomcat 5.5.9
without the cluster fix pack (Bug 34389) So you have a regression there, which
should be fixed. Anyway, this bug isn't INVALID, it's either a bug, or a
WONTFIX, so I reopen it. But you should really fix that, since many load
balancers don't support tomcat's sticky sessions.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-07 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540





--- Additional Comments From [EMAIL PROTECTED]  2005-09-07 12:42 ---
Created an attachment (id=16329)
 -- (http://issues.apache.org/bugzilla/attachment.cgi?id=16329action=view)
the test case and config files


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-07 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2005-09-07 12:48 ---
How about not filing a bug ? It should be evident sticky sessions are mandatory,
or you're going to run into problems.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

2005-09-07 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36540.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36540





--- Additional Comments From [EMAIL PROTECTED]  2005-09-07 13:21 ---
*** Bug 36542 has been marked as a duplicate of this bug. ***

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]