[ https://issues.jboss.org/browse/WFLY-10130?page=com.atlassian.jira.plugin... ] Jörg Bäsner updated WFLY-10130: ------------------------------- Description: Having a Timer annotated like: {code} @Schedule(second = "*/15", minute = "*", hour = "*", persistent = true) public void timeoutMethod() { {code} and a server configuration like: {code:xml} <timer-service thread-pool-name="default" default-data-store="clustered-store"> <data-stores> <database-data-store name="clustered-store" datasource-jndi-name="java:jboss/datasources/ExampleDS"/> </data-stores> </timer-service> {code:xml} will lead to a hanging Timer in case the Database connection is not available and only a restart of the server will recover the Timer. was: Having a Timer annotated like: @Schedule(second = "*/15", minute = "*", hour = "*", persistent = true) public void timeoutMethod() { and a server configuration like: <timer-service thread-pool-name="default" default-data-store="clustered-store"> <data-stores> <database-data-store name="clustered-store" datasource-jndi-name="java:jboss/datasources/ExampleDS"/> </data-stores> </timer-service> will lead to a hanging Timer in case the Database connection is not available and only a restart of the server will recover the Timer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)