[
https://issues.apache.org/jira/browse/FELIX-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Rankin updated FELIX-6511:
--------------------------------
Description:
Shutting down the SCR does not cancel the {{changeCountTimer}} thread running
inside {{{}ComponentRegistry{}}}. This prevents the JVM from shutting down
cleanly after the OSGi framework has stopped.
In my case, the JVM hangs for 5 seconds between my `main` function returning
and my shutdown hooks starting. The JVM then exits normally, although the 5
second delay is unexpected.
was:
Shutting down the SCR does not cancel the `changeCountTimer` thread running
inside `ComponentRegistry`. This prevents the JVM from shutting down cleanly
after the OSGi framework has stopped.
In my case, the JVM hangs for 5 seconds between my `main` function returning
and my shutdown hooks starting. The JVM then exits normally, although the 5
second delay is unexpected.
> Felix SCR ComponentRegistry leaves Timer thread running on deactivation.
> ------------------------------------------------------------------------
>
> Key: FELIX-6511
> URL: https://issues.apache.org/jira/browse/FELIX-6511
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Environment: Linux x86_64, Java 11.
> Reporter: Chris Rankin
> Priority: Major
>
> Shutting down the SCR does not cancel the {{changeCountTimer}} thread running
> inside {{{}ComponentRegistry{}}}. This prevents the JVM from shutting down
> cleanly after the OSGi framework has stopped.
> In my case, the JVM hangs for 5 seconds between my `main` function returning
> and my shutdown hooks starting. The JVM then exits normally, although the 5
> second delay is unexpected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
