[
https://issues.jboss.org/browse/WFLY-12733?page=com.atlassian.jira.plugin...
]
Rhuan Rocha commented on WFLY-12733:
------------------------------------
[~cfang] thank you for clarifying. About the second option exposed by you, I agree, but I
think it should be configured and user should be able to enable and disable this
behavior.
EJB Timers: Forcing refresh timers in a database-data-store in a
clustered environment
--------------------------------------------------------------------------------------
Key: WFLY-12733
URL:
https://issues.jboss.org/browse/WFLY-12733
Project: WildFly
Issue Type: Feature Request
Components: EJB
Reporter: Rhuan Rocha
Assignee: Cheng Fang
Priority: Major
The EJB Timer has a way to persist timers in a database using datasources. It is
described
[
here|https://docs.jboss.org/author/display/WFLY10/EJB3+Clustered+Database...]. The
database-data-store has an attribute called refresh-interval that define a time in
milliseconds to refresh the timers reading the timers from database. Look this sample of
configuration.
{code:java}
<data-stores>
<file-data-store name="default-file-store"
path="timer-service-data" relative-to="jboss.server.data.dir"/>
<database-data-store name="clustered-store"
datasource-jndi-name="java:/jdbc/MyDataSource" partition="timer"
refresh-interval="60000" allow-execution="true"/>
</data-stores>
{code}
The RFE is to Wildfly provide a way to force the refresh programmatically.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)