Originally posted by Alecsandru Cocarla:
I saw you have another question about your application freezing because of a textfield. Are you sure it's not from the same problem?
Originally posted by Roberto Perillo:
Champ, all objects that will be sent from an RMI server to the client (and vice-versa) must implement the java.io.Serializable interface.
If the specified record is already locked by a different client, the current thread gives up the CPU and consumes no CPU cycles until the record is unlocked.
Originally posted by Andrew Monkhouse:
So leaving the record locked is fine, as long as you notify any clients waiting on the thread that they should try to get the lock again (at which point they should get a RecordNotFoundException or similar).
Do you also think that the deleteRecord should not unlock the record ?
Then the unlockRecord will fail in any case after the record is deleted.
Calling unlock on a deleted record is a nonsens in my opinion. What do you think ?