felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Toni Menzel (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-329) Calling Felix.stopAndWait() from Runtime.shutdownHook() freezes thread
Date Fri, 20 Jul 2007 21:34:06 GMT

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

Toni Menzel updated FELIX-329:
------------------------------

    Summary: Calling Felix.stopAndWait() from Runtime.shutdownHook() freezes thread  (was:
Calling Felix.stopAndWait() from Runtime.shutdownHook() freezed thread)

> Calling Felix.stopAndWait() from Runtime.shutdownHook() freezes thread
> ----------------------------------------------------------------------
>
>                 Key: FELIX-329
>                 URL: https://issues.apache.org/jira/browse/FELIX-329
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>         Environment: tested on trunk (r555374)
>            Reporter: Toni Menzel
>             Fix For: 1.0.0
>
>
> if a shutdownHook invokes Felix.stopAndWait() the monitor never gets notified and stays
"wait()" forever.
> Until now i haven't found a direct way to fix this behaviour "normally" but if we could
use the timeout version wait(int) instead of "wait()" this behaviour is not tied to the monitor.notifyAll()
functionality. (so perhaps its the better solution anyway and not just a workaround?)
> Toni

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message