glassfish_at_javadesktop.org wrote:
> 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.
>
At this point it seems to be a derby issue. I think the solution would
be to define indexes on the required columns. I will wait for a report
from hegalor's experiment to confirm.
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>