There is a problem with Windows Share and Java combination, in the File's canRead()/canWrite() APIs.
These APIs are returning true even if the particular file/directory does not expose that permission. This results in XDisk's permission checks, done during an operation itself, passing even if actual permissions don't exist. When XADisk proceeds to commit the changes, only then the lack of permissions result in exception. The XADisk instance would fail during commit and would make itself unavailable.
Workaround is to make sure to assign all needed permissions beforehand, when using windows share folders.