[
https://issues.jboss.org/browse/WFLY-8087?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-8087:
----------------------------------------
A bit more on why this happens.
We don't know if the statistics resource is going to be needed until Stage.RUNTIME, as
the statistics-enabled attribute allows expressions. Plus, we don't know the exact
statistics that will be available until runtime, as those are dependent on the DS/RA
implementation. So, the MRR is not registered until RUNTIME. But we don't allow
Resource tree changes after Stage.MODEL, and the MSC Service that does the MRR reg
can't safely hold a ref to the Resource tree beyond the scope of one op anyway (since
a later write op will clone the tree leaving the service with an stale copy.) So to work
around this the child statistics resource is always added.
A partial improvement on this is to not add it on an HC, since it's never relevant
there and the MRR will never be added. My PR does that.
Statistics Resources are being created without a corresponding
ManagementResourceRegistration
---------------------------------------------------------------------------------------------
Key: WFLY-8087
URL:
https://issues.jboss.org/browse/WFLY-8087
Project: WildFly
Issue Type: Bug
Components: JCA, JMS
Reporter: Brian Stansberry
Assignee: Brian Stansberry
While working on WFCORE-2286 I discovered that there are resources in the tree, at least
on the DC, for which there is no corresponding MRR. I believe [~pferraro] in some recent
work he's done has stumbled on a similar thing.
I found there were no MRRs for
/profile=*/subsystem=messaging-activemq/server=*/pooled-connection-factory=*/statistics=pool
/profile=*/subsystem=datasources/data-source=*/statistics=jdbc
/profile=*/subsystem=datasources/data-source=*/statistics=pool
I expect the latter two would be repeated for xa-data-source=*
Probably the lack of MRR is correct and the problem is the existence of the resource.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)