Boris Pran created WFLY-10388: --------------------------------- Summary: Persistent EJB timer timed_object_id naming discrepancy Key: WFLY-10388 URL: https://issues.jboss.org/browse/WFLY-10388 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 12.0.0.Final Reporter: Boris Pran 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.5.0#75005)