Mitesh, thanks for for post. Derby can be tricky when it comes to locking. So, is it really an Derby issue (=bug), or that Glassfish has problems with Derby's locking mechanisms (incompatible)? Maybe, this could be resolved by ensuring a certain ordering/synchronization within Glassfish's timer service.
PS.: I wonder if Derby continues to be bundled with GF. Or will it be replaced by MySQL in the future...
[Message sent by forum member 'markusoj' (markusoj)]
http://forums.java.net/jive/thread.jspa?messageID=307371