Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
9.5.1
-
None
-
Unknown
-
Description
So the old one keep running.
The scheduler would need to find out if the class come from a classloader associated to a namespace and register a listener to see that some JAR extension has been upgraded/uninstalled in that namespace.
Would be a bit easier if we introduce some more explicit ClassloaderResetedEvent event since the current scheduler is not supposed to care about extensions that much.
The current workaround is to stop and start the scheduler from the UI by hand after an upgrade.