[jboss-jira] [JBoss JIRA] (JGRP-1663) TimeScheduler3 could spawn too many threads

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791259#comment-12791259 ] 

Bela Ban commented on JGRP-1663:
--------------------------------

Reducing sock_conn_timeout in TCP will definitely help.
I'm closing this issue as TimeScheduler3 works the way it was designed.
                
> TimeScheduler3 could spawn too many threads
> -------------------------------------------
>
>                 Key: JGRP-1663
>                 URL: https://issues.jboss.org/browse/JGRP-1663
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.3.3
>            Reporter: Igor Mazur
>            Assignee: Bela Ban
>            Priority: Optional
>             Fix For: 3.4
>
>         Attachments: global.xml, site.xml
>
>
> With default timer thread pool settings this code could spawn thousands of threads:
> protected void submitToPool(final Task entry) {
>         try {
>             pool.execute(entry);
>         }
>         catch(RejectedExecutionException rejected) { // only thrown if rejection policy is "abort"
>             Thread thread=timer_thread_factory != null?
>               timer_thread_factory.newThread(entry, "Timer temp thread")
>               : new Thread(entry, "Timer temp thread");
>             thread.start();
>         }
>     }
> On my environment I got 19000 threads.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira