Hello,
Cocoon 2.1.9 introduced the concept of a lock in
AbstractCachingProcessingPipeline, an optimization to prevent
two concurrent requests from generating the same cached
content. The first request adds the pipeline key to the
transient cache to 'lock' the cache entry for that
Hi,
The crux is that the sub-pipeline is called twice within the context of
the master pipeline (once by the root pipeline, once by an include);
thus the pipeline keys which are the same are those for the
sub-pipeline, not the master pipeline.
My 'broken' pipeline is too complex to explain,
Hi,
The crux is that the sub-pipeline is called twice within the
context of
the master pipeline (once by the root pipeline, once by an include);
thus the pipeline keys which are the same are those for the
sub-pipeline, not the master pipeline.
My 'broken' pipeline is too complex
Hi Ard,
I've not tried the double-aggregate thing (yet), but I've now attached
to the bug a very simple repeatable test that demonstrates the lock up
as I've experienced it.
Have fun!
Ellis.
Ard Schrijvers wrote:
Hi,
The crux is that the sub-pipeline is called twice within the
context
Hello Ellis,
Hi Ard,
I've not tried the double-aggregate thing (yet), but I've now
attached
to the bug a very simple repeatable test that demonstrates
the lock up
as I've experienced it.
I do not doubt about your testsI will try to find some time to verify your
findings (and
