[opencms-dev] OpenCMS on multiple app servers

[apoorv.durga at wipro.com]

I believe there is a way to invalidate cache by adding request parameters to the URL. For example,  http://url?_flex=clearcache. So technically, we call call this url of App server B and it will remove all cache from App server B.

However, I'm still not sure what the URL part will be? Which page should I call on the second app server to remove cache?



> -----Original Message-----
> From: opencms-dev-bounces at opencms.org
> [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Tomáš Adámek
> Sent: Thursday, December 15, 2005 3:17 PM
> To: The OpenCms mailing list
> Subject: Re: [opencms-dev] OpenCMS on multiple app servers
>
> Hi,
>
> well I were trying to do so but with no success. There is
> some settings in opencms xml config files (opencms.properties
> in older version of opencms), you can try to play with
> cache/files values. Pls let me know, if it will work for you, thx.
>
> >Hi,
> >Thanks for the inputs. I thought of it but since Appserver 2
> would only be used when app server 1 is down, I think we will
> be able to minimize this. However, is there any documentation
> on how to invalidate cache on the other app server? I've 
> gone thru flex cache docs but haven't got too much of idea.
> >
> >Any pointers would be appreciated.
> >
> >BR,
> >Apoorv
> >
> >
> > 
> >
> >>-----Original Message-----
> >>From: opencms-dev-bounces at opencms.org
> >>   
> >>
> >
> > 
> >
> >>[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Tomáš Adámek
> >>Sent: Wednesday, December 14, 2005 3:41 PM
> >>To: The OpenCms mailing list
> >>Subject: Re: [opencms-dev] OpenCMS on multiple app servers
> >>
> >>   
> >>
> >
> > 
> >
> >
> > 
> >
> >>Hello,
> >>
> >>   
> >>
> >
> > 
> >
> >>there would be problem with internal opencms cache
> >>   
> >>
> >
> > 
> >
> >>implementation - opencms clears the cache when the
> >>   
> >>
> >
> > 
> >
> >>file/folder is published. So thats mean that if You will
> >>   
> >>
> >
> > 
> >
> >>publish some document on app1 server, it will be flushed from
> >>   
> >>
> >
> > 
> >
> >>cache - but app2 server has no mechanism to check if the
> >>   
> >>
> >
> > 
> >
> >>content of file was changed, so it will still show old
> >>   
> >>
> >
> > 
> >
> >>content of file until u will restart application.
> >>
> >>   
> >>
> >
> > 
> >
> >>You will have to implement some notice mechanism to clear
> >>   
> >>
> >
> > 
> >
> >>cache on app2 when you make publish action on app1 server.
> >>
> >>   
> >>
> >
> > 
> >
> >>This problem was on opencms 5 but i think, that same cache
> >>   
> >>
> >
> > 
> >
> >>mechanism is implemented on opencms 6 too.
> >>
> >>   
> >>
> >
> > 
> >
> >>>Our requirement is that if the server running opencms is
> >>>     
> >>>
> >
> > 
> >
> >>brought down,
> >>   
> >>
> >
> > 
> >
> >>>the content editors will still be able to contribute content
> >>>     
> >>>
> >
> > 
> >
> >>and users
> >>   
> >>
> >
> > 
> >
> >>>will be able to access the site.
> >>>For this, we are planning to have opencms deployed on two
> >>>     
> >>>
> >
> > 
> >
> >>app servers.
> >>   
> >>
> >>>There will be a single database and the app servers will NOT be
> >>>     
> >>>
> >
> > 
> >
> >>>clustered. OpenCMS on both the app servers will access the same
> >>>     
> >>>
> >
> > 
> >
> >>>database. Although this is not a completely fault tolerant
> >>>     
> >>>
> >
> > 
> >
> >>system but
> >>   
> >>
> >
> > 
> >
> >>>we are hoping to achieve our objective.
> >>>
> >>>However, i'm not sure if there are any implications of
> this approach.
> >>>For example, if we use App server A to publish content, will those
> >>>     
> >>>
> >
> > 
> >
> >>>changes be reflected in App server B? I am assuming it will
> >>>     
> >>>
> >
> > 
> >
> >>be the case
> >>   
> >>
> >
> > 
> >
> >>>because VFS and the database will still be same.
> >>>
> >>>we are using opencms 6.0.2 with weblogic.
> >>>
> >>>Any inputs will be much appreciated.
> >>>
> >>>BR,
> >>>/a
> >>>
> >>>
> >>>_______________________________________________
> >>>This mail is send to you from the opencms-dev mailing list
> To change
> >>>     
> >>>
> >
> > 
> >
> >>>your list options, or to unsubscribe from the list, please visit
> >>>     
> >>>
> >
> > 
> >
> >>>http://mail.opencms.org/mailman/listinfo/opencms-dev
> >>>
> >>>     
> >>>
> >
> > 
> >
> >
> > 
> >
> >
> > 
> >
> >
> > 
> >
> >
> > 
> >
> >>_______________________________________________
> >>This mail is send to you from the opencms-dev mailing list To
> >>   
> >>
> >
> > 
> >
> >>change your list options, or to unsubscribe from the list,
> >>   
> >>
> >
> > 
> >
> >>please visit http://mail.opencms.org/mailman/listinfo/opencms-dev
> >>
> >>   
> >>
> >
> >
> >
> >The information contained in this electronic message and any
> attachments to this message are intended for the exclusive
> use of the addressee(s) and may contain proprietary,
> confidential or privileged information. If you are not the
> intended recipient, you should not disseminate, distribute or
> copy this e-mail. Please notify the sender immediately and
> destroy all copies of this message and any attachments.
> >
> >
> >WARNING: Computer viruses can be transmitted via email. The
> recipient should check this email and any attachments for the
> presence of viruses. The company accepts no liability for any
> damage caused by any virus transmitted by this email.
> >
> >
> >www.wipro.com
> >
> >
> >_______________________________________________
> >This mail is send to you from the opencms-dev mailing list To change
> >your list options, or to unsubscribe from the list, please visit
> >http://mail.opencms.org/mailman/listinfo/opencms-dev
> > 
> >
>
>
>
>
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list To
> change your list options, or to unsubscribe from the list,
> please visit http://mail.opencms.org/mailman/listinfo/opencms-dev
>


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com