[ https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2650: ------------------------------------- Runtime version and Active Sessions are added as Runtime attributes of the Teiid Subsystem, so they are not part of the configuration like other attributes you see with the "read-resource". So, in the domain mode when you make a call {code} /profile=ha/subsystem=teiid:read-resource {code} it will only returns the configurable attributes. However, if you issue the command against a running node server like {code} /host=master/server=server-one/subsystem=teiid:read-resource {code} it will return right results, however there seems to another bug in AS code that is not being reported correctly. I see the invocations correctly. however, the correct way to look for attribute is to {code} /host=master/server=server-one/subsystem=teiid:read-attribute(name=runtime-version) {code} That does work! So, there is nothing Teiid can fix I can think of, unless we make this property static in the standalone.xml or domain.xml. The idea in AS is each server node could possibly running a different Teiid subsystem. Designer needs to probe first for available hosts, then select one, then probe for available servers under that group, then use equivalent to above to get the right version. -- 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