Transaction Deadlock Occurs When EJB Timers Are Used on Derby Database
Last updated on JULY 12, 2017
Applies to:Oracle GlassFish Server - Version 3.1.1 to 3.1.2 [Release 3.1]
Information in this document applies to any platform.
On GlassFish Server 3.1.x, when the EJB Timer service is used with the default embedded Derby Java Database, some of the EJB Timer operations might fail. The GlassFish Server logs shows that there is some transaction deadlock happening and one of the EJB timer operation running on one of the threads is rolled back. An example of this error is shown below:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms