Hi, I am seeing a thread leak in Sling Event 3.2.0 which is fixed in the TimedEventSender in 3.3.0, however Sling Event 3.2.0 depends on later versions of Commons Scheduler which has caused some issues upgrading. Class cast exceptions and some strange behaviour elsewhere. I suspect it can be fixed by updating enough bundles, but that is something I would like to avoid.
Would anyone have an objection if I backported the TimedEventSender from the tip of Trunk and did a maintenance release of Sling Event 3.2.0 (ie 3.2.1) with the same package dependency footprint as 3.2.0 ? If thats not ok, I can patch the bundle locally. Best Regards Ian BTW, I haven't checked if its possible to keep the package dependencies static, but I think it will be. BTW2, I think TimedEventSender is the source of the thread leak.... but I cant be certain until I patch and deploy the code.
