You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/07/05 13:17:49 UTC
[jira] Commented: (FELIX-2431) EventAdmin service unregistered but
not registered again on ConfigAdmin startup
[ https://issues.apache.org/jira/browse/FELIX-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885181#action_12885181 ]
Carsten Ziegeler commented on FELIX-2431:
-----------------------------------------
Does this not work or does it take too long? From your comment above I suspect the later while the bug title says different.
> EventAdmin service unregistered but not registered again on ConfigAdmin startup
> -------------------------------------------------------------------------------
>
> Key: FELIX-2431
> URL: https://issues.apache.org/jira/browse/FELIX-2431
> Project: Felix
> Issue Type: Bug
> Components: Event Admin
> Affects Versions: eventadmin-1.2.2
> Reporter: Thomas Diesler
> Assignee: Carsten Ziegeler
>
> In EventAdmin Configuration
> Object service = new ManagedService()
> {
> public synchronized void updated( Dictionary properties ) throws ConfigurationException
> {
> configure( properties );
> stop();
> start();
> }
> };
> The call to stop() does not return in a timely manner (i.e. it may take > 40sec). This is because the asyncronous thread pool cannot be closed properly. This condition occurs when eventadmin is started before configadmin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.