[JBoss JIRA] (WFLY-12733) EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-12733?page=com.atlassian.jira.plugin... ]
Cheng Fang edited comment on WFLY-12733 at 11/1/19 9:23 AM:
------------------------------------------------------------
[~rhn-support-rhsilva] I think TimerServiceImpl class is an internal implementation class and is not supposed to be directly accessed by applications. Although users can cast the standard javax.ejb.TimerService to the internal TimerServiceImpl, this type of usage is not supported and may change in the future. In this sense, adding methods to ejb timer internal classes to force refresh is not a viable option, IMHO. The other option is to have getTimers() method always refresh internally before returning results.
was (Author: cfang):
@reporter I think TimerServiceImpl class is an internal implementation class and is not supposed to be directly accessed by applications. Although users can cast the standard javax.ejb.TimerService to the internal TimerServiceImpl, this type of usage is not supported and may change in the future. In this sense, adding methods to ejb timer internal classes to force refresh is not a viable option, IMHO. The other option is to have getTimers() method always refresh internally before returning results.
> 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)
4 years, 5 months
[JBoss JIRA] (WFLY-12733) EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-12733?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-12733:
-----------------------------------
@reporter I think TimerServiceImpl class is an internal implementation class and is not supposed to be directly accessed by applications. Although users can cast the standard javax.ejb.TimerService to the internal TimerServiceImpl, this type of usage is not supported and may change in the future. In this sense, adding methods to ejb timer internal classes to force refresh is not a viable option, IMHO. The other option is to have getTimers() method always refresh internally before returning results.
> 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)
4 years, 5 months
[JBoss JIRA] (WFLY-12745) EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment
by Cheng Fang (Jira)
Cheng Fang created WFLY-12745:
---------------------------------
Summary: EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment
Key: WFLY-12745
URL: https://issues.jboss.org/browse/WFLY-12745
Project: WildFly
Issue Type: Feature Request
Components: EJB
Reporter: Cheng Fang
Assignee: Cheng Fang
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)
4 years, 5 months