You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2015/06/16 23:43:06 UTC
[jira] [Updated] (QPID-6450) [Java Broker] Use separate
configuration thread for each virtual host node
[ https://issues.apache.org/jira/browse/QPID-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey updated QPID-6450:
------------------------------
Status: Reviewable (was: In Progress)
> [Java Broker] Use separate configuration thread for each virtual host node
> --------------------------------------------------------------------------
>
> Key: QPID-6450
> URL: https://issues.apache.org/jira/browse/QPID-6450
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: 6.0 [Java]
>
>
> Currently all process of model object actions occurs on the same single broker wide thread. Instead we should have a separate thread per virtual host node for all actions on the corresponding virtual host and its children. The threads should correspond to the stores.
> Care should be taken that there can be no deadlock where the broker management thread awaits completion of a task on the virtual host thread, while the virtual host thread is awaiting the broker.
> It seems likely that we can assert that the virtual host thread should never make a synchronous call into the broker wide thread.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org