I am trying to get TWS working with XMetal 3.0 but when I open a document using web-folders, I receive the message ‘Cannot lock file’ and the document is opened read-only. When I check the TWS logs I get the following:

in StdErr:
Ctx(/taminowebdavserver) : Status code:404 request:R( /taminowebdavserver + /xp/test/. + null) msg:Not Found

in StdOut:
INFO [Thread-15] - PROPFIND = 207 Multi-Status (time: 10 ms) URI = /xp/test
INFO [Thread-15] - GET = 200 OK (time: 40 ms) URI = /xp/test/test.xml
WARN [Thread-15] - Not Found
INFO [Thread-15] - Rollback Transaction 9 xid Thread-15-1022082929399-9- in thread Thread-15
INFO [Thread-15] - PROPFIND = 207 Multi-Status (time: 20 ms) URI = /xp/test/.
INFO [Thread-15] - OPTIONS = 200 OK (time: 0 ms) URI = /xp/test/.
WARN [Thread-15] - Not Found
INFO [Thread-15] - Rollback Transaction 11 xid Thread-15-1022082929439-11- in thread Thread-15
INFO [Thread-15] - PROPFIND = 207 Multi-Status (time: 10 ms) URI = /xp/test/.
INFO [Thread-15] - PROPFIND = 207 Multi-Status (time: 0 ms) URI = /xp/test
INFO [Thread-15] - OPTIONS = 200 OK (time: 0 ms) URI = /xp/test/test.xml
INFO [Thread-15] - Rollback Transaction 14 xid Thread-15-1022082929509-14- in thread Thread-15
INFO [Thread-15] - LOCK = 423 Locked (time: 20 ms) URI = /xp/test/test.xml
INFO [Thread-15] - GET = 200 OK (time: 30 ms) URI = /xp/test/test.xml
INFO [Thread-15] - OPTIONS = 200 OK (time: 10 ms) URI = /xp/test/test.xml
INFO [Thread-15] - Rollback Transaction 17 xid Thread-15-1022082938532-17- in thread Thread-15
INFO [Thread-15] - LOCK = 423 Locked (time: 10 ms) URI = /xp/test/test.xml
INFO [Thread-15] - GET = 200 OK (time: 30 ms) URI = /xp/test/test.xml

What is the problem? It seems that my document (test.xml under folder ‘test’ in collection ‘xp’) cannot be found, but I can open (a copy of) it. XMetal says it cannot lock the file, the log shows a ‘423 Locked’ message.

Does anyone have TWS 3.1.2 running successfully with XMetal 3.0? Or did anyone solve a similar problem with another editor? Any help will be VERY welcome…

Hello,



There were actually 2 problems (We have finally tested with Xmetal 3.04.062).



1) The first open of a file reports “opened as read-only”. Reason: Some spelling mismatches in the I18N area (utf-8 verse UTF-8 and namespace names of d: verse D:) and utf-8 encoding problems. This left the file in a locked state. Anyway, if the unlock would have been called, this unlock had no effect, caused by a Xmetal problem of not enclosing the lock token. This problem occurs in V3122 only and is fixed in the current community versions.

2) Sub-sequent open of the same file reports “open as read-only”. This was caused by the hanging (not removed) lock token caused by Xmetal not enclosing the lock token at the unlock command.



Best regards,



Juergen Pill