[ https://issues.jboss.org/browse/AS7-5472?page=com.atlassian.jira.plugin.s... ] Mathieu Lachance updated AS7-5472: ---------------------------------- Summary: unavailable datasource statistics (was: datasource statistics) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-5472?page=com.atlassian.jira.plugin.s... ] Mathieu Lachance commented on AS7-5472: --------------------------------------- I'll build master and will check for it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-5472?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-5472: --------------------------------------- Ok, thanks for checking. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-5472?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-5472: --------------------------------------- Stefano, if the representation of this stuff looks right via the CLI, I suspect it's a problem in how the JMX view into the core management model is dealing with the description of datasource resources. When we added statistics=jdbc and statistics=pool to the description tree, it exposed a design flaw in what I originally did. The design was, for the "datasource" resource: {code} { "attributes" => { ... attributes }, "operations" => { ... operations }, "children" => { "statistics" => { "model-description" => { ... attributes, operations, children of generic 'statistics' children } } } } {code} This design assumed that all children of type 'statistics' have the same model-description. But in reality in some cases children are polymorphic, and for those we have: {code} { "attributes" => { ... attributes }, "operations" => { ... operations }, "children" => { "statistics" => { "jdbc" => { "model-description" => { ... attributes, operations, children of 'statistics=jdbc' children } }, "pool" => { "model-description" => { ... attributes, operations, children of 'statistics=pool' children } } } } } {code} This introduced another level that the JMX view logic probably doesn't handle. If the CLI view looks OK, I suggest you ping Kabir and I about this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-5472?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-5472: --------------------------------------- Yeah, I'm not arguing it's incorrect, just saying it's contrary to the original (broken) design, and that's a probable cause of the JMX problem. If so the fix is to adapt the JMX view logic to recognize and deal with this. In general we need to make it easy for clients to recognize this (which is a separate issue.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira