Re: Deadlock issue

Friday, April 20, 2012, 2:33:44 PM, Jacopo Cappellato wrote:

> Hi Daniel,
>
> On Apr 20, 2012, at 2:21 PM, Daniel Dekany wrote:
>
>> Friday, April 20, 2012, 10:37:52 AM, Jacopo Cappellato wrote:
>> 
>>> Daniel D., Daniel L.,
>>> 
>>> thanks to both of you for the valuable help.
>>> 
>>> I was able to find and fix the OFBiz code that was causing the
>>> multiple reload of Groovy related classes: in OFBiz there was cache
>>> object containing the parsed Groovy scripts that was not managed in
>>> a thread safe way.
>> 
>> So then can it still occur that a Groovy-script-class is reloaded even
>> if the script wasn't modified, only not so often?
>
> It should no more happen now: the OFBiz cache object is now
> properly synchronized and even if multiple threads will try to
> compile the same script only the first Groovy-script-class will be
> added to the cache and then used to renderthe freemarker template.
> After this change all "reload" messages from freemarker disappeared.

What I meant is that if these are in-memory-only classes, the Groovy
script cache might drops some of them sometimes. If it's that kind of
cache.

-- 
Best regards,
 Daniel Dekany


------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2