-
1. Re: Hello
jaysensharma Dec 4, 2015 9:55 PM (in response to sigminas)Not sure what do you mean by "jbos version EAP 6.2 /monitoring tool java/jmc" ?
However you can easily monitor the DataSource using the following kind of CLI Commands ($JBOSS_HOME/bin/jboss-cli.sh):
[standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS/statistics=pool:write-attribute(name=statistics-enabled,value=true) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS/statistics=pool:read-resource(include-runtime=true,include-defaults=true,recursive=true) { "outcome" => "success", "result" => { "ActiveCount" => "0", "AvailableCount" => "20", "AverageBlockingTime" => "0", "AverageCreationTime" => "0", "CreatedCount" => "0", "DestroyedCount" => "0", "InUseCount" => "0", "MaxCreationTime" => "0", "MaxUsedCount" => "0", "MaxWaitCount" => "0", "MaxWaitTime" => "0", "TimedOut" => "0", "TotalBlockingTime" => "0", "TotalCreationTime" => "0", "statistics-enabled" => true } }
-
2. Re: Hello
jaysensharma Dec 5, 2015 11:19 AM (in response to sigminas)By JMC you mean Java Mission Control which is present inside the "$JAVA_HOME/bin/jmc". Then this JMC startup is controlled by options specified in the "jmc.ini" file, which is located in the "JAVA_HOME/bin" directory.
So please try this:
Edit the "$JAVA_HOME//bin/jmc.ini" file and add the "jboss-client.jar" as following in it:
-Xbootclasspath/a:/PATH/TO/jboss-eap-6.4/bin/client/jboss-client.jar
Then start the "jmc" and then create a new connection using the URL as following (for example here "localhost" is the JBoss Management Address or specify the IP Address if you started your JBoss Management interface or the remoting address of server.
service:jmx:remoting-jmx://localhost:9999
Then navigate the MBean browser present in the JMC console and there you should be able to see the DataSource related data.