[JBoss JIRA] (WFLY-10584) Timer repeats uncontrolled
by Jörg Bäsner (JIRA)
[ https://issues.jboss.org/browse/WFLY-10584?page=com.atlassian.jira.plugin... ]
Jörg Bäsner updated WFLY-10584:
-------------------------------
Steps to Reproduce:
These steps can be applied on a RHEL system to reproduce the error:
# install a vanilla Wildfly 13.0.0.Final
# deploy the attached [^playground-jar.jar]
# set the system timezone to {{Helsinki, Finland (EEST, UTC+03)}}
# set the system date to the 24th of March 2018 ({{sudo date +%Y%m%d -s "20180324"}})
# set the system time to 23:59:30 ({{sudo timedatectl set-time 22:59:30}})
# start the server using the {{standalone.xml}} configuration
was:
These steps can be applied on a RHEL system to reproduce the error:
# install a vanilla Wildfly 13.0.0.Final
# deploy the attached playground-jar.jar
# set the system timezone to {{Helsinki, Finland (EEST, UTC+03)}}
# set the system date to the 24th of March 2018 ({{sudo date +%Y%m%d -s "20180324"}})
# set the system time to 23:59:30 ({{sudo timedatectl set-time 22:59:30}})
# start the server using the {{standalone.xml}} configuration
> Timer repeats uncontrolled
> --------------------------
>
> Key: WFLY-10584
> URL: https://issues.jboss.org/browse/WFLY-10584
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 13.0.0.Final
> Reporter: Jörg Bäsner
> Assignee: Jörg Bäsner
> Attachments: playground-jar.jar
>
>
> Given an hourly timer like this:
> {code}
> @Schedule(hour = "*", persistent = false)
> public void hourlyTimer(Timer timer) {
> long methodEntryTime = System.currentTimeMillis();
> ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
> ZoneId.systemDefault());
> logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
> millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
> }
> {code}
> Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
> {noformat}
> 23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10584) Timer repeats uncontrolled
by Jörg Bäsner (JIRA)
[ https://issues.jboss.org/browse/WFLY-10584?page=com.atlassian.jira.plugin... ]
Jörg Bäsner updated WFLY-10584:
-------------------------------
Steps to Reproduce:
These steps can be applied on a RHEL system to reproduce the error:
# install a vanilla Wildfly 13.0.0.Final
# deploy the attached playground-jar.jar
# set the system timezone to {{Helsinki, Finland (EEST, UTC+03)}}
# set the system date to the 24th of March 2018 ({{sudo date +%Y%m%d -s "20180324"}})
# set the system time to 23:59:30 ({{sudo timedatectl set-time 22:59:30}})
# start the server using the {{standalone.xml}} configuration
> Timer repeats uncontrolled
> --------------------------
>
> Key: WFLY-10584
> URL: https://issues.jboss.org/browse/WFLY-10584
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 13.0.0.Final
> Reporter: Jörg Bäsner
> Assignee: Jörg Bäsner
> Attachments: playground-jar.jar
>
>
> Given an hourly timer like this:
> {code}
> @Schedule(hour = "*", persistent = false)
> public void hourlyTimer(Timer timer) {
> long methodEntryTime = System.currentTimeMillis();
> ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
> ZoneId.systemDefault());
> logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
> millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
> }
> {code}
> Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
> {noformat}
> 23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10584) Timer repeats uncontrolled
by Jörg Bäsner (JIRA)
[ https://issues.jboss.org/browse/WFLY-10584?page=com.atlassian.jira.plugin... ]
Jörg Bäsner updated WFLY-10584:
-------------------------------
Attachment: playground-jar.jar
> Timer repeats uncontrolled
> --------------------------
>
> Key: WFLY-10584
> URL: https://issues.jboss.org/browse/WFLY-10584
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 13.0.0.Final
> Reporter: Jörg Bäsner
> Assignee: Jörg Bäsner
> Attachments: playground-jar.jar
>
>
> Given an hourly timer like this:
> {code}
> @Schedule(hour = "*", persistent = false)
> public void hourlyTimer(Timer timer) {
> long methodEntryTime = System.currentTimeMillis();
> ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
> ZoneId.systemDefault());
> logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
> millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
> }
> {code}
> Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
> {noformat}
> 23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10586) messaging-activemq journal-datasource attribute is missing requirement.
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-10586:
----------------------------------
Summary: messaging-activemq journal-datasource attribute is missing requirement.
Key: WFLY-10586
URL: https://issues.jboss.org/browse/WFLY-10586
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 13.0.0.Final
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
The journal-datasource attribute in the messaging-activemq's server resource is representing the name of a DataSource resource.
The capability is correctly added as a capability dependency when the server is added but the journal-datasource attribute is not listing it as a capabilty reference in its definition.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10586) messaging-activemq journal-datasource attribute is missing requirement
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-10586?page=com.atlassian.jira.plugin... ]
Jeff Mesnil updated WFLY-10586:
-------------------------------
Summary: messaging-activemq journal-datasource attribute is missing requirement (was: messaging-activemq journal-datasource attribute is missing requirement.)
> messaging-activemq journal-datasource attribute is missing requirement
> ----------------------------------------------------------------------
>
> Key: WFLY-10586
> URL: https://issues.jboss.org/browse/WFLY-10586
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 13.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> The journal-datasource attribute in the messaging-activemq's server resource is representing the name of a DataSource resource.
> The capability is correctly added as a capability dependency when the server is added but the journal-datasource attribute is not listing it as a capabilty reference in its definition.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10585) BanTransitiveDependencies enforcer violations while building wildfly-galleon-pack module on IBM jdk
by Petr Kremensky (JIRA)
Petr Kremensky created WFLY-10585:
-------------------------------------
Summary: BanTransitiveDependencies enforcer violations while building wildfly-galleon-pack module on IBM jdk
Key: WFLY-10585
URL: https://issues.jboss.org/browse/WFLY-10585
Project: WildFly
Issue Type: Bug
Components: Build System
Reporter: Petr Kremensky
Assignee: Jason Greene
Building WildFly: Full Galleon Pack using IBM jdk fails with enforcer BanTransitiveDependencies violation.
*reproduce*
{noformat}
wildfly] $ mvn package -pl galleon-pack
...
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (ban-transitive-deps) @ wildfly-galleon-pack ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
org.wildfly:wildfly-galleon-pack:pom:14.0.0.Beta1-SNAPSHOT
org.apache.cxf:cxf-rt-features-logging:jar:3.2.4-jbossorg-1:compile has transitive dependencies:
xalan:xalan:jar:2.7.1.jbossorg-4:compile
xalan:serializer:jar:2.7.1.jbossorg-4:compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 21.949 s
[INFO] Finished at: 2018-06-18T13:30:17+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (ban-transitive-deps) on project wildfly-galleon-pack: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
{noformat}
*workaround*
Skip enforcer by adding {{-Denforcer.skip=true}} property
*environment*
{noformat}
$ mvn -version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
Maven home: /usr/lib/maven
Java version: 1.8.0_171, vendor: IBM Corporation
Java home: /usr/lib/java/ibm-java-8.0-5.16/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.16.15-300.fc28.x86_64", arch: "amd64", family: "unix"
$ git rev-parse --short HEAD
4eff06230b
{noformat}
*ibm jdk download*
https://developer.ibm.com/javasdk/downloads/sdk8/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10584) Timer repeats uncontrolled
by Jörg Bäsner (JIRA)
[ https://issues.jboss.org/browse/WFLY-10584?page=com.atlassian.jira.plugin... ]
Jörg Bäsner updated WFLY-10584:
-------------------------------
Description:
Given an hourly timer like this:
{code}
@Schedule(hour = "*", persistent = false)
public void hourlyTimer(Timer timer) {
long methodEntryTime = System.currentTimeMillis();
ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
ZoneId.systemDefault());
logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
}
{code}
Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
{noformat}
{{23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]}}
{noformat}
was:
Given an hourly timer like this:
{code}
@Schedule(hour = "*", persistent = false)
public void hourlyTimer(Timer timer) {
long methodEntryTime = System.currentTimeMillis();
ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
ZoneId.systemDefault());
logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
}
{code}
Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
{{23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]}}
> Timer repeats uncontrolled
> --------------------------
>
> Key: WFLY-10584
> URL: https://issues.jboss.org/browse/WFLY-10584
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 13.0.0.Final
> Reporter: Jörg Bäsner
> Assignee: Jörg Bäsner
>
> Given an hourly timer like this:
> {code}
> @Schedule(hour = "*", persistent = false)
> public void hourlyTimer(Timer timer) {
> long methodEntryTime = System.currentTimeMillis();
> ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
> ZoneId.systemDefault());
> logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
> millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
> }
> {code}
> Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
> {noformat}
> {{23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]}}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10584) Timer repeats uncontrolled
by Jörg Bäsner (JIRA)
[ https://issues.jboss.org/browse/WFLY-10584?page=com.atlassian.jira.plugin... ]
Jörg Bäsner updated WFLY-10584:
-------------------------------
Description:
Given an hourly timer like this:
{code}
@Schedule(hour = "*", persistent = false)
public void hourlyTimer(Timer timer) {
long methodEntryTime = System.currentTimeMillis();
ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
ZoneId.systemDefault());
logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
}
{code}
Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
{noformat}
23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
{noformat}
was:
Given an hourly timer like this:
{code}
@Schedule(hour = "*", persistent = false)
public void hourlyTimer(Timer timer) {
long methodEntryTime = System.currentTimeMillis();
ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
ZoneId.systemDefault());
logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
}
{code}
Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
{noformat}
{{23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]}}
{noformat}
> Timer repeats uncontrolled
> --------------------------
>
> Key: WFLY-10584
> URL: https://issues.jboss.org/browse/WFLY-10584
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 13.0.0.Final
> Reporter: Jörg Bäsner
> Assignee: Jörg Bäsner
>
> Given an hourly timer like this:
> {code}
> @Schedule(hour = "*", persistent = false)
> public void hourlyTimer(Timer timer) {
> long methodEntryTime = System.currentTimeMillis();
> ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
> ZoneId.systemDefault());
> logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
> millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
> }
> {code}
> Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
> {noformat}
> 23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10584) Timer repeats uncontrolled
by Jörg Bäsner (JIRA)
[ https://issues.jboss.org/browse/WFLY-10584?page=com.atlassian.jira.plugin... ]
Jörg Bäsner updated WFLY-10584:
-------------------------------
Description:
Given an hourly timer like this:
{code}
@Schedule(hour = "*", persistent = false)
public void hourlyTimer(Timer timer) {
long methodEntryTime = System.currentTimeMillis();
ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
ZoneId.systemDefault());
logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
}
{code}
Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
{{23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]}}
was:
Given an hourly timer like this:
@Schedule(hour = "*", persistent = false)
public void hourlyTimer(Timer timer) {
long methodEntryTime = System.currentTimeMillis();
ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
ZoneId.systemDefault());
logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
}
Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
{{23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]}}
> Timer repeats uncontrolled
> --------------------------
>
> Key: WFLY-10584
> URL: https://issues.jboss.org/browse/WFLY-10584
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 13.0.0.Final
> Reporter: Jörg Bäsner
> Assignee: Jörg Bäsner
>
> Given an hourly timer like this:
> {code}
> @Schedule(hour = "*", persistent = false)
> public void hourlyTimer(Timer timer) {
> long methodEntryTime = System.currentTimeMillis();
> ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
> ZoneId.systemDefault());
> logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
> millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
> }
> {code}
> Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
> {{23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 10) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month