My application processes events. These events are sent to registered users. These events can be deleted when they reach a certain age. There is a thread to send events to registered users and there is another thread to delete old events. The thread sending an event should lock it from the thread that deletes old events. Each thread uses its own connection to the database. In the sending thread, I've tried using a SELECT ... FOR UPDATE and setting the ResultSet.CONCUR_UPDATABLE on the prepare statement. In both cases, the thread that deletes events deleted the event being held by the sending thread. The default isolation level and autocommit options are used.
Thanks in advance...Walter -- View this message in context: http://www.nabble.com/Row-Locking-tp23333804p23333804.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
