[
https://issues.apache.org/jira/browse/QPID-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754012#comment-15754012
]
Lorenz Quack edited comment on QPID-7560 at 12/16/16 10:11 AM:
---------------------------------------------------------------
I don't think the analysis "the only thing that causes a VH to go into
{{ERROR}} (sic) is a failure to schedule the housekeeping task" is correct.
That seems to be the only code in {{AbstractVirtualHost}} but there are other
places that set the state to {{ERRORED}}. The one I found was
ACO#handleExceptionOnOpen.
However I don't think that changes anything about the patch
was (Author: lorenz.quack):
I don't think the analysis "the only thing that causes a VH to go into
{{ERROR}} is a failure to schedule the housekeeping task" is correct. That
seems to be the only code in {{AbstractVirtualHost}} but there are other places
that set the state to {{ERRORED}}. The one I found was
ACO#handleExceptionOnOpen.
However I don't think that changes anything about the patch
> AbstractVirtualHost defines two state transitions from ERROR to ACTIVE
> ----------------------------------------------------------------------
>
> Key: QPID-7560
> URL: https://issues.apache.org/jira/browse/QPID-7560
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Minor
> Fix For: qpid-java-6.2, qpid-java-6.1.1, qpid-java-6.0.6
>
>
> The current implementation of AbstractVirtualHost defines two state
> transitions from ERROR=>ACTIVE. The state change mechanics could choose
> either which could lead to undesired results.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
