Re: [Exist-open] users deleted

[W.S. H. <ws...@gm...>]

Apologies, I promised to make a new tread. Please leave it for now.
Wolfgang, I sent you the now corrupt *.dbx files. Unfortunately the log was
already overwritten. Hope this helps.

I'll drop this until next year. Have a good one everyone.


2013/12/19 W.S. Hager <ws...@gm...>

> Is there any way I can prevent errors in XSLT to flood the JVM?
>
>
> 2013/12/19 <wol...@ex...>
>
> A faulty xslt loop seemed to be the cause of this. Perhaps it would be
>> better to post a new thread/scratch on this specific issue, but my main
>> concern is that things like this that instantly hangs Java, possibly
>> resulting in data corruption doesn't help to promote the good things about
>> eXist, and I think you should be made aware of this.
>>
>>
>> Several people are already working to improve crash recovery and right
>> now there are two concrete things you can do to help:
>>
>> 1) whenever you had to kill eXist for whatever reason, please archive
>> your data directory *before* you take further action, i.e. immediately
>> after the kill. In particular, I need the .log and .dbx files before they
>> are changed by a restart. If the restart fails or results in errors, send
>> me the archived data, so I can debug the recovery process. Debugging such a
>> failing archive indeed helped me to hunt down a pretty critical bug
>> yesterday.
>>
>> 2) help us test the redesigned crash recovery code available in this
>> branch:
>>
>> https://github.com/wolfgangmm/exist/tree/feature/recovery
>>
>> I’d like to merge this into develop, but I need to be sure it does not
>> introduce new issues. The branch corresponds to the current eXist-db
>> develop, but features rewritten crash recovery code for the indexes which
>> should help to avoid recovery failures.
>>
>> Wolfgang
>>
>
>
>
> --
>
> W.S. Hager
> Lagua Web Solutions
> http://lagua.nl
>



-- 

W.S. Hager
Lagua Web Solutions
http://lagua.nl