GlassFish Server Cluster EJB Timer Migration Sometimes Fails And Deletes All Timers
Last updated on NOVEMBER 05, 2016
Applies to:Oracle GlassFish Server - Version 2.1.1 and later
Information in this document applies to any platform.
Problem has been observed when one instance of GlassFish cluster is shutting down. Timers owned by this instance should be migrated to another instance, but instead all timers owned by the application component are deleted from the store (including timers owned by the second instance). The problem occurs in random fashion - not every shutdown of the GlassFish instance causes timers deletion, but can be reconstructed repeatedly - once in several shutdowns (about 10).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms