i think locking happens in a filter... look for DisableCacheFilter or similar
On Tue, Aug 18, 2009 at 5:56 AM, Nathan Beemer wrote:
> Out of curiosity... is this due to some synchronized collection(s) that back
> the cache?
> they block until the RequestCycle is over in order to empty them as per
Out of curiosity... is this due to some synchronized collection(s) that back
the cache?
they block until the RequestCycle is over in order to empty them as per the
org.apache.tapestry.disable-caching directive.. thus all other Page access
which can use the cache must wait?
On Sun, Aug 16, 2009 at
it was indeed set to true. and it was indeed causing the blocking
many thanks!
On Aug 16, 2009, at 8:12 PM, Andreas Andreou wrote:
see if you have
org.apache.tapestry.disable-caching set to true
It is possible that this might be causing that
On Mon, Aug 17, 2009 at 2:54 AM, Nathan
Beemer
see if you have
org.apache.tapestry.disable-caching set to true
It is possible that this might be causing that
On Mon, Aug 17, 2009 at 2:54 AM, Nathan Beemer wrote:
>
> I have an IEngineService implementation that simply has Thread.sleep(3);
> in the service() implementation.
>
> I have a sim
I have an IEngineService implementation that simply has
Thread.sleep(3); in the service() implementation.
I have a simple Page with a ServiceLink that calls this IEngineService.
When I click the ServiceLink which causes Thread.sleep() to be
invoked, ALL other Page access blocks until t
