You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2011/03/25 00:36:05 UTC
[jira] [Commented] (FELIX-2891) remote shell bundle starts
non-daemon threads
[ https://issues.apache.org/jira/browse/FELIX-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011010#comment-13011010 ]
Richard S. Hall commented on FELIX-2891:
----------------------------------------
I think the main issue is that the spec doesn't require that the framework start a non-daemon thread, so if someone wanted to start a framework instance and have remote access to it, then they'd be responsible for creating a bundle for doing so. For the Felix framework, this wouldn't be an issue, since we create a single non-daemon thread for the Event Dispatcher.
Technically, the bundle is allowed to have non-daemon threads as long as it is in the ACTIVE state. It should be able to expect to be stopped to discard its non-daemon threads.
> remote shell bundle starts non-daemon threads
> ---------------------------------------------
>
> Key: FELIX-2891
> URL: https://issues.apache.org/jira/browse/FELIX-2891
> Project: Felix
> Issue Type: Bug
> Components: Remote Shell
> Affects Versions: shell.remote-1.1.2
> Reporter: Sahoo
>
> I see the telnetconsole listener thread spawned by Felix Remote Shell is a non-daemon thread:
> "telnetconsole.Listener" prio=10 tid=0x76fe4400 nid=0x1d75 runnable [0x792fe000]
> Can it be turned into a daemon?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira