[
https://issues.apache.org/jira/browse/QPID-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8230:
-----------------------------
Description:
When startup of stopped Virtual Host fails (for example, due to defect
QPID-8229) some of its children could be recovered and stored in virtual host
internal data structures. The subsequent virtual host restarts can fail with
another error "409 - Child of type XXXX already exists with id of YYYY". This
error masks the original error causing virtual host failure in first place.
No error is reported into the broker logs. If original error causing first
virtual host startup failure can be fixed, the VHN restart or Broker restart
can resolve "409 - Child of type XXXX already exists with id of YYYY"
was:
When Virtual Host startup fails (for example, due to defect QPID-8229) some of
its children could be recovered and stored in virtual host internal data
structures. The subsequent virtual host restarts can fail with another error
"409 - Child of type XXXX already exists with id of YYYY". This error masks the
original error causing virtual host failure in first place.
No error is reported into the broker logs. If original error causing first
virtual host startup failure can be fixed, the VHN restart or Broker restart
can resolve "409 - Child of type XXXX already exists with id of YYYY"
> [Broker-J] Virtual Host children can be partially recovered and left in
> memory on failed Virtual Host startup
> -------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8230
> URL: https://issues.apache.org/jira/browse/QPID-8230
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.6
> Reporter: Alex Rudyy
> Priority: Major
>
> When startup of stopped Virtual Host fails (for example, due to defect
> QPID-8229) some of its children could be recovered and stored in virtual host
> internal data structures. The subsequent virtual host restarts can fail with
> another error "409 - Child of type XXXX already exists with id of YYYY". This
> error masks the original error causing virtual host failure in first place.
> No error is reported into the broker logs. If original error causing first
> virtual host startup failure can be fixed, the VHN restart or Broker restart
> can resolve "409 - Child of type XXXX already exists with id of YYYY"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
