[opencms-dev] publish problem alpha 2

Wed Dec 15 11:24:45 CET 2004

Hans,

there is just one FlexCache for all sites of an installation of OpenCms, so
it can't be that publishing site A will not clear site B. If someting is
published regardless of which site it belongs to, the whole FlexCache is
flushed. 

I'm not saying that there is no hidden issue in the FlexCache code. However,
to reproduce this I require a way to re-produce the issue, otherwise I won't
be able to fix it. 

Best Regards,
Alex.

Alexander Kandzior
Alkacon Software - The OpenCms Experts
http://www.alkacon.com

> -----Original Message-----
> From: opencms-dev-bounces at opencms.org 
> [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Hans 
> van der Linden
> Sent: Wednesday, December 15, 2004 9:34 AM
> To: The OpenCms mailing list
> Subject: RE: [opencms-dev] publish problem alpha 2
> 
> Hi Alex,
> 
> It's not a client side cache problem but a flexcache issue.
> I found the exact location of the problem. Let's say I have a 
> multiple config of the OpenCMS.
> 
> www.siteA.com
> www.siteB.com
> 
> I access the workplace via www.workplaceA.com. I enter the 
> workplace and change a file in SiteA. I than publish the 
> Offline project.
> This publish action will clear the flexcache for 
> www.workplaceA.com BUT NOT for www.siteA.com. I checked this 
> by entering the workplace via www.siteA.com/.../system/login. 
> (this can still be done even if siteA is not defined as the 
> workplace URL) I than go to the flexcache in the 
> administration view and see that this is not cleared. After 
> manualy clearing the flexcache here I see the latest changes in SiteA.
> 
> The strange thing is this didn't happen in the beginning but 
> only after growing in content.
> 
> Any ideas?
> 
> Hans
> 
> PS I did sent a e-mail to support to open an email incident 
> but had no reaction so far.
> 
> 
> 
> 
> 
> 
> 
> -----Oorspronkelijk bericht-----
> Van: opencms-dev-bounces at opencms.org
> [mailto:opencms-dev-bounces at opencms.org]Namens Alexander Kandzior
> Verzonden: dinsdag 14 december 2004 14:35
> Aan: 'The OpenCms mailing list'
> Onderwerp: RE: [opencms-dev] publish problem alpha 2
> 
> 
> This is because of the caching of the browser. OpenCms will 
> use the expiration date set on the resource and send this as 
> http expiration header to the client. In case the expiration 
> is far in the future, the maximum "age" a page can have is 24 hours.
> 
> This is true for all online content. Logging in to the 
> workplace will force a "no cache" header for all requests 
> since obviously here the content must be refreshed on a 
> continuous basis.
> 
> To be clear, in case you change a page and publish, it is of 
> course updated in the OpenCms VFS and all users who request 
> the page the first time will see the updated content. 
> However, if you have an old version cached by the browser, it 
> dosen't even connect to OpenCms, it just displays the old 
> version out of his cache. You can verify this by using a tool 
> like "live http headers" available for Firefox. You can also 
> just clear the cache of the browser to see the updated 
> version. Apparently this is so even if you set the browserto 
> "reload page every time", don't ask me why this is.
> 
> To make the expiration update more frequently, use the 
> "timeout" flex cache directive on any resource included in 
> the template, or on the template itself. Keep in mind that 
> this is actually a feature to reduce server load.
> Sending a "no cache" every time (or allowing only a very short cache
> timeout) on a production site for content that changes only 
> frequently (say once a day or so) isn't usually a good idea.
> 
> Best Regards,
> Alex.
> 
> Alexander Kandzior
> Alkacon Software - The OpenCms Experts
> http://www.alkacon.com
> 
> 
> 
> > -----Original Message-----
> > From: opencms-dev-bounces at opencms.org
> > [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Hans van der 
> > Linden
> > Sent: Tuesday, December 14, 2004 2:12 PM
> > To: The OpenCms mailing list
> > Subject: RE: [opencms-dev] publish problem alpha 2
> >
> > It seems to be a typical multi site issue. If you have configured a 
> > different URL (hostname) as <workplace-server> in your 
> > opencms-system.xml as your website URL (hostname) the problem can 
> > occur but when workplace-server and website URL
> > (hostname) are the same the problem is gone.
> >
> > Anyone any suggestions?
> >
> > Hans
> >
> >
> > -----Oorspronkelijk bericht-----
> > Van: opencms-dev-bounces at opencms.org
> > [mailto:opencms-dev-bounces at opencms.org]Namens Hans van der Linden
> > Verzonden: maandag 13 december 2004 14:09
> > Aan: The OpenCms mailing list
> > Onderwerp: [opencms-dev] publish problem alpha 2
> >
> >
> > Hi
> >
> > In Alpha 2 I have a strange problem. Publishing a html page from 
> > offline to online does not always result in an update of the online 
> > file when surfing to the website (by typing the URL in the 
> browser). 
> > Strange enough, selecting the file from the workplace in de online 
> > project DOES show the most recent update. Only when I 
> reboot Tomcat i 
> > will see the update in both ways. Anyone an idea where to look. 
> > Flexcache? Tomcat cache?
> >
> > Thanks
> >
> > Hans
> >
> > Windows 2003 server webedition
> > Apache Tomcat 5.0.28
> > OpenCms 5.5.3
> > JDK : j2sdk1.4.2_03
> > Database : mysql-4.0.21-nt
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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
> >
> >
> 
> 
> 
> _______________________________________________
> 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
> 
> 