Hi France,
I have finalized the WebDAV rewritings. The warning you observed
shouldn’t occur anymore (the same applies to the returned stack trace,
which was a consequence of the default user not being assigned to the
internal locks).
Have fun while testing,
Christian
[1]
Hi,
The first round of tests looks good. We'll try it in production and see how
it responds with multiple users.
The only issue (warning not error) I got was when trying to open a file if
the server is busy with a process. The message is :
[qtp1635546341-17] WARN com.bradmcevoy.http.LockInfo -
I believe we have fixed the reported issue. Furthermore, we didn’t
manage to trigger any of the exceptions (EOF, etc.) anymore. The new
snapshot is available.
Cheers,
Christian
On Fri, May 18, 2018 at 2:08 PM, France Baril
wrote:
> Awesome, any progress is good.
Awesome, any progress is good. We've been dealing with that lock issue for
the longest time, but it took a while to figure out how to replicate it
systematically. It was always so random. I'll see with the client when we
can upgrade and will let you know how it goes.
On Thu, May 17, 2018 at 9:05
Hi France,
Some updates:
• I fixed the locking bug that caused a null pointer exception.
• As you probably know, the WebDAV locks were organized in an
additional ~webdav database on disk. I decided to change this quite
fundamentally: From now on, the locks will be kept in main-memory.
Locks
Dear France,
A first update:
I noticed that the oXygen file access while updating the database
causes various exceptions (which are written to the BaseX logs). As a
result, I also get duplicate files in the database. I will try to find
out if this is something we can resolve, or if it goes back
Hi France,
I’ve just returned after a little break. Thanks for the elaborated
instructions; I’ll follow the described steps in the course of this
week.
Best,
Christian
On Sun, May 13, 2018 at 3:36 PM, France Baril
wrote:
> Hi,
>
> Just wondering if this slipped
Hi,
Just wondering if this slipped through the cracks.
On Wed, May 2, 2018 at 1:11 PM, France Baril
wrote:
> Hi,
>
> We've been having this issue for a while and we think resolving it may be
> the key to resolving an intermittent server 500 error that we've been
>
Hi,
We've been having this issue for a while and we think resolving it may be
the key to resolving an intermittent server 500 error that we've been
having.
When a user tries to save a file while a batch process is running, BaseX
saves duplicates of the file.
How to reproduce:
1) Take a fresh
9 matches
Mail list logo