[
https://issues.redhat.com/browse/WFLY-10388?page=com.atlassian.jira.plugi...
]
Lukas Vydra commented on WFLY-10388:
------------------------------------
Hi, I'm not able to reproduce this behaviour, are you still able to reproduce it? If
so, could you please provide us with more detailed reprosteps, configuration, etc. ?
Thank you
Persistent EJB timer timed_object_id naming discrepancy
-------------------------------------------------------
Key: WFLY-10388
URL:
https://issues.redhat.com/browse/WFLY-10388
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 12.0.0.Final
Reporter: Boris Pran
Assignee: Lukas Vydra
Priority: Major
Persistent EJB timers created declaratively (with @Schedule) create timed_object_id
without version information while timers created using TimerService API include version
info from deployment unit.
This way after version upgrade @Schedule timers survive but TimerService API created ones
are lost and need to be created again.
I also seems that old timers remain created or at least their definitions can be seen in
jboss_ejb_timer table.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)