>Well, my primary concern was that I don't want _other_ hosts to join my
>cluster not the other way around, so I am guessing I have to limit my
>mcast invitations and tcp traffic to relevant parties only?

that is exactly the point I was trying to make. Setup your security in the
OS that way you get more performance out of tomcat.
If you allow mcast traffic from other hosts into your machine, you are
already taking up resources.

Filip


-----Original Message-----
From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 04, 2004 2:22 PM
To: Tomcat Users List
Subject: RE: Tomcat 5.5 In-Memory Session Replication


did you try replication with 5.0.27?
if that works for you, then for sure something broke.
5.5 is still in dev mode, so you can't bank on everything working quit yet
:)

Filip

-----Original Message-----
From: Tomcat Newbie [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 04, 2004 4:51 AM
To: Tomcat Users List
Subject: RE: Tomcat 5.5 In-Memory Session Replication


Thanks again, Filip. I am sending this response to document my
experience for others.

> set up machines to only access mcast and tcp traffic from certain IPs and
> certain ports.

Well, my primary concern was that I don't want _other_ hosts to join my
cluster not the other way around, so I am guessing I have to limit my
mcast invitations and tcp traffic to relevant parties only? :-)

> ok, I haven't tested replication on 5.5 yet myself, I've been to busy with
> corporate world.
> but from what I am reading, is that the replication valve is not issuing
the
> transfer or session deltas. Maybe something broke...we'll have to check

Sounds about right. Logs show original and replicate session creation.
Most of the time, SessionListener will log correct original session
attribute name, but null value. However, even when it does log both name
and value, still there is no replication done.

> you do have the replication valve set up in server.xml right?

I believe so. Default setup and I saw no instructions for additional
setup anywhere for replication valve, other than the filter options.


I figured I ventured into something too "bleeding edge" for me (I did so
mainly because Jakarta site said that 5.5 was branched off from 5.0.27).
So I went back to 5.0.28. Then, after spending a few hours pointlessly
watching the logs for any activity other than mcast membership
registrations, to my surprise, I discovered that the session attributes
were replicating beautifully on 5.0.28, but without any logging. Yup,
with all debug="" cranked up all the way to 9 or 10. Go figure! Glad it
works, though.

I also found a link for JDBC persistence manager (http://www.ingrid.org/
jajakarta/tomcat/tomcat-4.0b5/src/catalina/docs/JDBCStore-howto.html),
so I might go in that direction, since such setup would certainly
address my security concerns. Similar, but less complete documentation
is available for 5.x (http://jakarta.apache.org/tomcat/tomcat-5.0-doc/
config/manager.html). I have played with built-in MySQL replication and
so far I have no complaints about its performance for low-load servers.
I just need to make sure that it stores sessions in MySQL all the time,
not just swapped. MySQL will take care of the rest.


Regards,

Ed


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004


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

Reply via email to