Hi Edgar, what you see is normal cache behavior. When first request for any given resource (big file in your case) comes, Magnolia will create cache entry if such resource can be cached and will start serving this resource. Any subsequent requests for such resource will be blocked by Magnolia and forced to wait until resource in question is fully served and cached. Since it's possible that generating of said resource fails for whatever reason, Magnolia will not block other requests forever, but only for preset time (10 seconds by default) after which time it would either return subsequent request for same resource to user. While processing the first request for given resource, Magnolia will realize that it is big file and will stop caching and will mark cache entry for such resource accordingly. Once this is done there's no issue w/ serving said resource to multiple users in parallel.
IIRC the reason for implementing this was to prevent errors in the templates or models (e.g. infinite loop, waiting for external resource w/o timeout, etc.) from exhausting servers worker threads, however by doing so it creates problem when serving big files. Perhaps this should be configurable and behavior should be different for dms and data based resources. Disabling cache for big resources is indeed a solution for such problem. HTH, Jan On Aug 23, 2012, at 6:48 PM, Edgar Vonk (via Magnolia Forums) wrote: > Hi, > > we seem to have the same issue but then with Magnolia 4.5 and large files in > the data module. > > We see that with high traffic Magnolia can not serve these files (20MB FLV > files in this case) and the browser requests of end users time out. > > WARN info.magnolia.module.cache.filter.CacheFilter > CacheFilter.java(doFilter:137) 23.08.2012 18:04:22 The following URL was > blocked for longer than 10 seconds and has timed-out. The request has been > blocked as another request is already processing the same resource. > [url=http://localhost:8080/data/test/test.flv] > > I tried disabling the cache by adding an excludes to /data and to my surprise > this seemed to solve the issue! I test it with a simple JMeter script. > > Could it be that there is an issue with large files in the cache in Magnolia > 4.5, possibly related to the data module? > > cheers, > > Edgar > > -- > Context is everything: > http://forum.magnolia-cms.com/forum/thread.html?threadId=aa9ad5f2-5e7e-4ab6-b3c7-921065664420 > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
