Dear devs, I'm wondering how runtime attributes (such as ConnectionCount for a ManagedConnection Pool, or Thread's QueueSize) could be gathered on AS 7. By using CLI ? Using a recursive read-resource, just dumps the resource startup properties.....

use read-attribute:

Am 09.05.2011 um 13:31 schrieb Francesco Marchioni: > Dear devs, > I'm wondering how runtime attributes (such as ConnectionCount for a ManagedConnection Pool, or Thread's QueueSize) could be gathered on AS 7. > By using CLI ? Using a recursive read-resource, just dumps the resource startup properties..... use read-attribute: [domain@localhost:9999 connector=http] :read-attribute(name=maxTime) { "outcome" => "success", "result" => "no metrics available", "compensating-operation" => undefined } _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

There are two reason you don't get actual values:

a) not the most recent AS7 build b) no data available

There are two reason you don't get actual values: a) not the most recent AS7 build b) no data available This is what I get when building the recent master: [domain@localhost:9999 /] /profile=default/subsystem=datasources/data-source="java:/H2DS":read-resourc(include-runtime=true) { "outcome" => "success", "result" => { "connection-url" => "jdbc:h2:mem:test;DB_CLOSE_DELAY=-1", "driver-class" => "org.h2.Driver", "jndi-name" => "java:/H2DS", "driver" => "org.h2.Driver#1.2", "pool-name" => "H2DS", "use-java-context" => true, "enabled" => true, "pool-prefill" => false, "pool-use-strict-min" => false, "user-name" => "sa", "password" => "sa", "MaxWaitTime" => "no metrics available", "ActiveCount" => "no metrics available", "CreatedCount" => "no metrics available", "MaxWaitCount" => "no metrics available", "use-fast-fail" => undefined, "background-validation" => undefined, "max-pool-size" => undefined, "PreparedStatementCacheMissCount" => "no metrics available", "TotalBlockingTime" => "no metrics available", "AverageCreationTime" => "no metrics available", "PreparedStatementCacheAddCount" => "no metrics available", "PreparedStatementCacheDeleteCount" => "no metrics available", "PreparedStatementCacheHitCount" => "no metrics available", "DestroyedCount" => "no metrics available", "AverageBlockingTime" => "no metrics available", "idle-timeout-minutes" => undefined, "MaxCreationTime" => "no metrics available", "TotalCreationTime" => "no metrics available", "PreparedStatementCacheAccessCount" => "no metrics available", "AvailableCount" => "no metrics available", "blocking-timeout-wait-millis" => undefined, "background-validation-minutes" => undefined, "MaxUsedCount" => "no metrics available", "min-pool-size" => undefined, "TimedOut" => "no metrics available", "PreparedStatementCacheCurrentSize" => "no metrics available" }, "compensating-operation" => undefined } On May 9, 2011, at 2:10 PM, Francesco Marchioni wrote: > By using > /subsystem=datasources/data-source="java:/H2DS":read-resource(include-runtime=true) > produces the just the initial set of properties, though it may be that simply no runtime information is available at the moment...... > > [localhost:9999 /] /subsystem=datasources/data-source="java:/H2DS":read-resource > (include-runtime=true) > { > "outcome" => "success", > "result" => { > "connection-url" => "jdbc:h2:mem:test;DB_CLOSE_DELAY=-1", > "driver-class" => "org.h2.Driver", > "jndi-name" => "java:/H2DS", > "driver" => "org.h2.Driver#1.2", > "pool-name" => "H2DS", > "use-java-context" => true, > "enabled" => true, > "pool-prefill" => true, > "pool-use-strict-min" => false, > "user-name" => "sa", > "password" => "sa", > "share-prepared-statements" => false, > "background-validation" => false, > "use-fast-fail" => false, > "validate-on-match" => false, > "idle-timeout-minutes" => undefined, > "blocking-timeout-wait-millis" => undefined, > "background-validation-minutes" => undefined, > "min-pool-size" => undefined, > "max-pool-size" => undefined > }, > "compensating-operation" => undefined > }