You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (Updated) (JIRA)" <ji...@apache.org> on 2012/02/13 15:23:00 UTC

[jira] [Updated] (FELIX-3348) StartLevel thread may terminate on uncaught exception

     [ https://issues.apache.org/jira/browse/FELIX-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated FELIX-3348:
-------------------------------------

    Attachment: FELIX-3348.patch

Proposed patch:
  - catching IllegalStateException rescheduling the start level change
  - catching other exceptions just continuing

Depending on the cause of the IllegalStateException, this may in fact cause the startlevel switch to be endlessly done. Maybe not scheduling the start level again is better ...
                
> StartLevel thread may terminate on uncaught exception
> -----------------------------------------------------
>
>                 Key: FELIX-3348
>                 URL: https://issues.apache.org/jira/browse/FELIX-3348
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: framework-4.0.2
>            Reporter: Felix Meschberger
>         Attachments: FELIX-3348.patch
>
>
> It looks like an uncaught exception is able to terminate the StartLevel thread thus causing the framework to not be properly controllable.
> Sample issue: Felix.setActiveStartLevel may throw IllegalStateException if global lock cannot be acquired. This exception is not caught and causes StartLevel thread to terminate.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira