The file locking mechanism implemented with JLan3.7.5

[james]

We conducted the several test cases on file locking mechanism of JLan3.7.5 in three scenarios with different applications, including MS Office Word2003, Photoshop, OpenOffice. the interesting thing is  : there is different result with different application on the file locking. three testing scenarios are:
1. Remote Lock/Local Open   
2. Local Lock/Remote Open
3. Remote Lock/Remote Open

here is the results listed below:
Application                         RemoteLock/LocalOpen              LocalLock/RemoteOpen                  RemoteLock/RemoteOpen
MS Office Word2003(MNP)       S(Batch oplock granted)                         S                                            S(Batch oplock granted)
MSOffice Word2003(JLan)      F(No oplock granted)                           S                                      F(No oplock granted)
PhotoShop(MNP)                         F(Pessimistic Lock)                 F(Pessimistic Lock)                    F(Pessimistic Lock)
PhotoShop(JLan)                         F(Pessimistic Lock)                 F(Pessimistic Lock)                     F(Pessimistic Lock)
OpenOffice(MNP)                        S(Batch oplock granted)                      S                                                         S
OpenOffice(JLan)                 S(No oplock granted)                F(after selection of the file type ,   F(No oplock granted)
                                                                                                  the file can’t open with a error
                                                                                                 coming out.)   

*: S: Succeeded;  F:Failed

how to explain these interesting test results we got with JLan3.7.5?    Hope your reply!

Mionet

James

[bbp]

I did similar tests that gave me catastrophic results such as data lost or file deletion.
Example:
Setup:
* 1 server with JLAN running (CIFS)
* 1 client Windows XP with MsWord 2002
* 1 client Windows XP with MsWord 2007

Normal beaviour (this sequence work as expected):
1. Open a doc file with MsWord 2007 (I assume it's locking it)
2. Open the same file with MsWord 2002 (the file is locked and I can see it in RO)

Unexpected beaviour (resulting with file lost):
1. Open a doc file with MsWord 2002 (I assume it's locking it)
2. Open the same file with MsWord 2007 (the file is probably locked by MsWord 2002 but MsWord 2007 open it in RW)
3. Modify and save the file opened with MsWord 2007 (I think at this time, MsWord 2007 steal the lock)
4. Modify and save the file opened with MsWord 2002 (MsWord 2002 think it has the lock)
Result: MsWord 2002 display an error (something like "Can not save the file") and the file is deleted from the server. It's not visible anymore from MsWord 2002 client but it's still visible on the MsWord 2007 client. After the network drive are unmapped and mapped again, the file is lost forever.

That situation is not an exception; it append every time this sequence is repeated. Unfortunatly, that's the kind of treatment my WCM have to do.

I hope someone have a solution. Otherwie, I will have to look for an other solution.

Thanks