Some more follow up on this. I was told that derby locks table during
execution of select. The offending query reported by you will be
executed when getTimer() is called. This query will result in a table
scan since the current schema for timer does not define any indexes on
CONTAINERID. If this query is called frequently in parallel, it might
explain the behavior. I was told that setting property
"derby.locks.monitor=true" will print out diagnostic information in
derby.log to confirm this. If this is confirmed, you can try modifying
schema for the timer database (it resides in
${com.sun.aas.instanceRoot}/lib/databases/ejbtimer ) to define index on
required field.
Thanks,
Mitesh
glassfish_at_javadesktop.org wrote:
> Hi!
>
> I've added this line... Perhaps it will happen again.
> [Message sent by forum member 'hegalor' (hegalor)]
>
> http://forums.java.net/jive/thread.jspa?messageID=304291
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>