Here is some pseudo code for how I have my "book" method:
Here is my problem. I would like to throw a runtime exception in the lock method if an InterruptedException is thrown. If this happens, the record is never locked. In my unlock method, I immediately perform two checks: 1 to see if the recNo is locked and 1 to see if the current thread is the owner of the lock on the recNo. If not, I throw a RecordNotFoundException.
I don't expect an InterruptedException to ever occur, but if it does, it will basically get destroyed by the RecordNotFoundException. The client then gets notified that it's trying to unbook a method that doesn't exist/it doesn't own, which isn't what I really want to report.
The VERY last line of my lock method is putting the recNo in my HashMap. So I think it's safe to say that if the method returns without throwing an exception, it was successful. So is it OK to have my the code to book ordered like this:
This way, any exception thrown in the lock method continues to bubble up and I am sure that the unbook method is only called after a successful lock?
posted 7 years ago
In case anybody is interested.... I couldn't bring myself to leave the lock method outside of the try block, so here's what I ended up doing: