[
https://issues.apache.org/jira/browse/QPID-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532270#comment-15532270
]
Lorenz Quack commented on QPID-7438:
------------------------------------
Answers to open questions:
* Do not use the {{changesConfiguredObjectState}} for
{{VH#import-/exportMessageStore}} methods. Instead manually move relevant
parts of the operation to the config thread and include the state assertion in
those sections.
* As mentioned in the previous point. The relevant part should be put on the
config thread manually and include the state assertion. It is ok to do this
potential long running operation on the VH config thread because the VH is
stopped anyway and the rest of the broker should be unaffected.
* As a pragmatic solution set {{changesConfiguredObjectState}} to false and
add a comment why. In the implementation then retrieve the cert in the Http
thread and only move setting of the attribute to the config thread.
* No. But we should make sure the relevant sections are thread safe. Ensure
correct use of volatile.
> ACL provider and AutoGeneratedSelfSignedKeyStore modify configured state
> without using the configuration task executor
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7438
> URL: https://issues.apache.org/jira/browse/QPID-7438
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
>
> By design, any changes to a CO's configured state must be made by the
> configuration task executor. There are managed operations on
> AutoGeneratedSelfSignedKeyStore, RuleBasedAccessControlProvider, and
> AclFileAccessControlProvider which violate this rule.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
