[jboss-jira] [JBoss JIRA] Resolved: (JGRP-683) Provide hooks to enable creation of all daemon threads

[Bela Ban (JIRA)]

     [ http://jira.jboss.com/jira/browse/JGRP-683?page=all ]

Bela Ban resolved JGRP-683.
---------------------------

    Resolution: Done

Fixed on CVS head and 2.6 branch

> Provide hooks to enable creation of all daemon threads
> ------------------------------------------------------
>
>                 Key: JGRP-683
>                 URL: http://jira.jboss.com/jira/browse/JGRP-683
>             Project: JGroups
>          Issue Type: Task
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6.2, 2.7
>
>         Attachments: bla.java
>
>
> Goal: to enable a developer to setup JGroups to use only daemon threads. Default will still be that IO bound threads are non-daemons
> Jon Richards wrote:
> > It works OK for the thread pools used by TP but a couple of problems:
> >
> > Problem 1: I need to kludge it a bit: it turns out that I need to do a
> > channel.connect() before I can modify/set the TP thread pools because
> > the thread pools are created in TP.start(). This means that non-daemon
> > threads can get created before I have a chance to modify the setting.
> What if I check in TP.start() if thread_pool/oob_thread_pool is already set and don't create a thread pool of already set ? Then you could create a JChannel, set the thread pool(s) and then call JChannel.connect().
> > Problem 2: there are other threads at the transport level that get
> > created using ProtocolStack.getThreadFactory() and there is not way to
> > override how this thread factory gets created.
> I could provide setters for the 2 thread factories in ProtocolStack and make them non-final. Would that help ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira