I just tried changing to tomcat-replication

and well, that didn't go as well as I wished! :)

Seams like the setAttribute, getAttribute and sessionCreation does work.
Both my server gets the replication messages.

My problem is that the browse never gets the request back! Everything looks
done on the tomcat side but the client never get the response content.

I tried removing the ReplicationValve and I can get the page back, but
replication doesn't occur (duh!) :)

So, here is my log file of the server that received the request:

---- Begin of a request log --------

09:24:38 StandardManager[/BusinessPortalWB]: [InMemoryReplicationManager]
Replicated Session created at lin-rap-ldev:32890 with
ID=29913859C07BCA38595DA243D1D5AB33
09:24:38 StandardManager[/BusinessPortalWB]: [InMemoryReplicationManager]
writeObject() storing session 29913859C07BCA38595DA243D1D5AB33
09:24:39 StandardManager[/BusinessPortalWB]: [InMemoryReplicationManager]
InMemoryReplicationManager.handle(): received message [dst: 228.1.2.3:45566,
src: lin-rap-ldev:32890 (1 headers), size = 607 bytes]
09:24:40 StandardManager[/BusinessPortalWB]: [InMemoryReplicationManager]
InMemoryReplicationManager.handle(): received message [dst: 228.1.2.3:45566,
src: lin-rap-ldev:32890 (1 headers), size = 553 bytes]
09:24:40 StandardManager[/BusinessPortalWB]: [InMemoryReplicationManager]
setAttribute called:
        Name=businessportal.lock;
[EMAIL PROTECTED]
        Debug info=SessionManager.java:55
09:24:43 StandardManager[/BusinessPortalWB]: [InMemoryReplicationManager]
getAttribute called:
        Name=businessportal.lock;
[EMAIL PROTECTED]
        Debug info=SessionManager.java:114
09:24:43 StandardManager[/BusinessPortalWB]: [InMemoryReplicationManager]
InMemoryReplicationManager.handle(): received message [dst: 228.1.2.3:45566,
src: lin-rap-ldev:32890 (1 headers), size = 810 bytes]
09:24:43 StandardManager[/BusinessPortalWB]: [InMemoryReplicationManager]
setAttribute called:
        Name=com.cognicase.businessportal.common.usercontext;
value={com.cognicase.businessportal.common.sessionmanager=1069683880243,
businessportal.mapping_stack=[]}
        Debug info=SessionManager.java:158
09:24:43 StandardManager[/BusinessPortalWB]: [InMemoryReplicationManager]
InMemoryReplicationManager.handle(): received message [dst: 228.1.2.3:45566,
src: lin-rap-ldev:32890 (1 headers), size = 359 bytes]
09:24:43 StandardManager[/BusinessPortalWB]: [InMemoryReplicationManager]
setAttribute called:
        Name=businessportal.language; value=en
        Debug info=SessionManager.java:159
09:24:43 ReplicationValve[/BusinessPortalWB]: [NEIL] [Thread-22]  [1]
Regular request completed in 4985ms.

------- Done ----------

What is a "Regular request" ??

The page I use to test it is a servlet GET with a Requestforward to a jsp
file.

Any insight would be welcomed.

Thanks,

Jean-Philippe

-----Original Message-----
From: Filip Hanik [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2003 4:45 PM
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: Re: tomcat-jg vs tomcat-replication


I would say, use tomcat-replication,
I'm the developer of both, and if you have questions and need help, I only
support tomcat-replication, unless you pay me to support tomcat-jg :)

Filip
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 21, 2003 11:57 AM
Subject: tomcat-jg vs tomcat-replication


Hi,

I'm running Tomcat 4.1.18 in production and needing session replication.
I've been able to get tomcat-jg up and running. But after reading some mail
on the tomcat user mailling list, fillip seam to say that this version won't
work with tomcat 4.1.x and that we should use the tomcat-replication (beta
from TC5).

Any advantages to uses the 2nd one? (NIO vs javagroup?) Bugs ?

Just don't want to use the javagroup one now and find out in some weeks that
it's wrecking havoc with our transactionnal servers!

Thanks for your time

Jean-Philippe B�langer
CGI


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

Reply via email to