Re: [Exist-development] possible issue with controller.xql in database with latest security changes

[James F. <jam...@ex...>]

apologies, all works once I forced rebuild which I thought I had done
int he first place .

ta, J

On 10 September 2010 15:05, James Fuller <jam...@ex...> wrote:
> latest trunk
>
> J
>
> On 10 September 2010 15:00, Dmitriy Shabanov <sha...@gm...> wrote:
>> On Fri, 2010-09-10 at 14:51 +0200, James Fuller wrote:
>>> Hello,
>>>
>>> I updated to latest trunk and a controller.xql that worked in the
>>> database all of a sudden stopped working and throws the following
>>> error
>>>
>>> 2010-09-10 14:49:07,655 [eXistThread-22] WARN
>>> (ReentrantReadWriteLock.java [release]:305) - Possible lock problem:
>>> thread Thread[eXistThread-22,5,main] released a lock on /db/testing it
>>> didn't hold. Either the thread was interrupted or it never acquired
>>> the lock. The lock was owned by: null
>>
>> I did see it before refactoring, it something else. what revision?
>>
>> --
>> Cheers,
>>
>> Dmitriy Shabanov
>>
>