roller-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leon Messerschmidt" <>
Subject RE: Roller on a clustered Tomcat Environment
Date Wed, 18 Jul 2007 02:22:58 GMT

I've got as far as:

1.  The search index is going to be somewhat of a problem.  There will
need to be some extra development to use a central search engine such as

2.  The roller_data directory will need to live on a location (NFS
perhaps) that is accessible to all instances of roller

3.  We'll have to turn caching off entirely or look into distributed

4.  We'll have to turn off pinging in all the instances except for one.

Anything else that I should be aware of?  Anybody care to help me out?

~ Leon

-----Original Message-----
From: Leon Messerschmidt []

Sent: Monday, 16 July 2007 1:54 PM
Subject: RE: Roller on a clustered Tomcat Environment

And I promise to use better language if I update docs ;-)  
English is my second language and it was before my first cup of coffee.
Cut me some slack!

-----Original Message-----
From: Leon Messerschmidt []

Sent: Monday, 16 July 2007 10:45 AM
Subject: Roller on a clustered Tomcat Environment


We're deploying roller in a fairly high availability environment and I
need to run roller on a Tomcat clustered environment.  I noticed bits
and peaces being mentioned in but not much
documentation.  Can someone please point me in the right direction?

If there is not much that is written down at the moment I'll be willing
add some information to the wiki (or install docs) as I go along.

~ Leon

This email, including attachments, is intended only for the addressee
and may be confidential, privileged and subject to copyright.  If you
have received this email in error, please advise the sender and delete
it.  If you are not the intended recipient of this email, you must not
use, copy or disclose its content to anyone.  You must not copy or 
communicate to others content that is confidential or subject to 
copyright, unless you have the consent of the content owner.

View raw message