You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have used Quartz for many years to handle our job scheduling, most recently for quite a while on Wildfly 24 and Java 8. We are now migrating to Wildfly 34 and Java 17. I was having issues with the latest stable release of Quartz and saw that Quartz 2.5.0 was available on GitHub so I'm trying it.
The scheduler seems to fire up OK, but I can't get the Ram jobs to run using the old EJB3InvokerJob due to changes in obtaining an InitialContext and the fact the code can't seem to invoke the jobs. I was wondering if anyone has had any experience with this migration and might have some advice to offer.
I saw where somebody had migrated Quartz 2.3.2 to Java 17 using OpenRewrite. Would that be a better approach? We've been using Quartz for so long I'd hate to even try to find a different job scheduler and try to migrate everything we've got to it.
Any help or advice would be greatly appreciated. I figure we're not the only ones out there trying this.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We have used Quartz for many years to handle our job scheduling, most recently for quite a while on Wildfly 24 and Java 8. We are now migrating to Wildfly 34 and Java 17. I was having issues with the latest stable release of Quartz and saw that Quartz 2.5.0 was available on GitHub so I'm trying it.
The scheduler seems to fire up OK, but I can't get the Ram jobs to run using the old EJB3InvokerJob due to changes in obtaining an InitialContext and the fact the code can't seem to invoke the jobs. I was wondering if anyone has had any experience with this migration and might have some advice to offer.
I saw where somebody had migrated Quartz 2.3.2 to Java 17 using OpenRewrite. Would that be a better approach? We've been using Quartz for so long I'd hate to even try to find a different job scheduler and try to migrate everything we've got to it.
Any help or advice would be greatly appreciated. I figure we're not the only ones out there trying this.
Beta Was this translation helpful? Give feedback.
All reactions