[
https://issues.apache.org/jira/browse/QPID-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15485385#comment-15485385
]
Rob Godfrey commented on QPID-7279:
-----------------------------------
1.1 - Oops - fixed
2.1 - Oops (again) - fixed
2.2 - Agreed - Fixed
3.1 - No the method is recording the fact that this is the first time the VHost
has been opened. The problem here is that we generally don't "create" the
vhost, instead we create a store with records that gets recovered, so stuff
that we would want to do in onCreate doesn't happen.
3.2 - This, to me, is the expected behaviour. If someone has somehow gone in
and purposefully deleted the standard exchanges, then we should leave it be.
Sure the vhost would then be "non AMQP compliant" but then in any sane
configuration we'd probably never suggest people use the default exchanges
(other than the no-name exchange), and instead set up custom exchanges which
can be permissioned appropriately
4.1 - Agreed - fixed
5. I think we should probably separate this into a new JIRA. I agree that it
would make most sense to try to make a base class or helper class to do the
state management rather than have the same code reimplemented for every store.
> [Java Broker] with config encryption creating a JDBC VirtualHost fails
> ----------------------------------------------------------------------
>
> Key: QPID-7279
> URL: https://issues.apache.org/jira/browse/QPID-7279
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Lorenz Quack
> Assignee: Rob Godfrey
> Fix For: qpid-java-6.1
>
>
> If configuration encryption is enabled on the broker creating a JDBC
> VirtualHost via the WMC fails with the following error:
> {{422 - Encrypted value is not valid Base 64 data: 'myPassword'}}
> Also we might not want to log the content of the invalid data due to its
> potential sensitive nature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
