[jboss-jira] [JBoss JIRA] (WFCORE-398) Avoid running out of threads when connecting to the DC from a slave to pull down missing data

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved WFCORE-398.
-------------------------------------
    Fix Version/s:     (was: 1.0.0.Beta1)
       Resolution: Out of Date


I don't believe this thread starvation problem still exists, as the pool used for these requests is not limited. Emmanuel, please re-open if I'm incorrect.

> Avoid running out of threads when connecting to the DC from a slave to pull down missing data
> ---------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-398
>                 URL: https://issues.jboss.org/browse/WFCORE-398
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Kabir Khan
>            Assignee: Emanuel Muckenhuber
>            Priority: Blocker
>
> For WFLY-259 when a slave connects to the DC to pull down missing data, it does this by either getting a lock for the DC, or by joining the permit of the existing DC lock if the request to update a slave's server-config was executed as part of a composite obtaining a lock on the DC.
> The way it works at present there is a thread per slave which is blocked until the transaction completes. The DC threads are a finite resource, so a large number of slaves trying to pull down dats will cause deadlock



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)