[
https://issues.jboss.org/browse/WFLY-9553?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-9553:
----------------------------------------
[~jmesnil] I would have done that except the attribute supports expressions.
You can actually use AD.resolveModelAttribute(...) in Stage.MODEL and it would work fine
except for vault expressions during boot. Vault expressions are not resolvable until the
vault is installed in Stage.RUNTIME.
PooledConnectionFactoryAdd adds a resource with no registration
---------------------------------------------------------------
Key: WFLY-9553
URL:
https://issues.jboss.org/browse/WFLY-9553
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 11.0.0.Final
Reporter: Brian Stansberry
Assignee: Jeff Mesnil
Priority: Minor
When working on WFCORE-2930 I was investigating discrepancies in mbean counts generated
via the method in that fix vs current code. I discovered one in WildFly's
messaging-activemq that is a result of a statistics resource being added to the resource
tree even if attribute that triggers registration of the related
ManagementResourceRegistration isn't set. So we have an undescribed resource.
This likely has no other impact than a slightly inaccurate result from
MBeanServerConnection.getMBeanCount() but we don't want this kind of thing anyway.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)