Session Replication
- From: "Lonnie" <lmatsuno (at) nwgeo.com>
- Date: Wed, 17 May 2006 08:34:48 -0600
Figured it out. Rebooted my servers. I suspect that some modifications I
made were not recognized until the reboot. Should have thought of it
sooner.
-----Original Message-----
From: Lonnie [mailto:lmatsuno (at) nwgeo.com]
Sent: Tuesday, May 16, 2006 4:52 PM
To: users (at) tomcat.apache.org
Subject: ***SUSPECT*** Session Replication
Hi,
I'm having a bit of difficulty getting session replication working with 2
servers running tomcat 5.5.16. I have configured apache to load balance and
fail over when one tomcat stops. I've been able to get the tomcat servers
to fail over.
I have also had limited success in getting the session replication to work.
The session is replicated in the second server and takes over when the first
server stops, but when the first server comes back up, the sessions get
messed up.
I'm thinking that it may have something to do with the replication member
address added on my second server.
Any thoughts? Thanks.
Lonnie
Heres a snippet of my log.
INFO: Server startup in 5728 ms
May 16, 2006 4:20:56 PM org.apache.catalina.cluster.tcp.SimpleTcpCluster
memberAdded
INFO: Replication member
added:org.apache.catalina.cluster.mcast.McastMember[tcp://127.0.0.2:8015,cat
alina,127.0.0.2,8015, alive=2]
May 16, 2006 4:20:56 PM
org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread
INFO: Create sender [/127.0.0.2:8,015] queue thread to tcp background
replication
May 16, 2006 4:20:57 PM org.apache.catalina.cluster.tcp.SimpleTcpCluster
logSendMessage
INFO: SEND May 16, 2006:4:20:57 PM 3 127.0.0.2:8,015
SESSION-STATE-TRANSFERED/wms
May 16, 2006 4:20:57 PM org.apache.catalina.cluster.tcp.SimpleTcpCluster
logReceiveMessage
INFO: RECEIVE May 16, 2006:4:20:57 PM 4 127.0.0.2:8,015 GET-ALL-/wms true
May 16, 2006 4:20:57 PM
org.apache.catalina.cluster.tcp.FastAsyncSocketSender$FastQueueThread
pushQueuedMessages
WARNING: Unable to asynchronously send session with
id=[SESSION-STATE-TRANSFERED/wms] - message will be ignored.
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:207)
at
org.apache.catalina.cluster.tcp.DataSender.createSocket(DataSender.java:704)
at
org.apache.catalina.cluster.tcp.DataSender.openSocket(DataSender.java:679)
at
org.apache.catalina.cluster.tcp.DataSender.pushMessage(DataSender.java:803)
at
org.apache.catalina.cluster.tcp.FastAsyncSocketSender$FastQueueThread.pushQu
euedMessages(FastAsyncSocketSender.java:476)
at
org.apache.catalina.cluster.tcp.FastAsyncSocketSender$FastQueueThread.run(Fa
stAsyncSocketSender.java:442)
Regards.
Lonnie Matsuno
(403) 539-9548
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe (at) tomcat.apache.org
For additional commands, e-mail: users-help (at) tomcat.apache.org