I am trying to monitor my connection between wildfly and my DB with the help of Zabbix. I have used JMX to monitor other components like heap memory etc. And I want to use JMX to monitor the connection. Can anyone please help me with this? Thank you
Related
I'm using M0 Cloud Managed MongoDB. I'm facing with the problem of 500 connections limit. I've checked full of docs to restart the connections but I can't manage to find Restart in Clusters Menu in Cloud Manager. Do I miss something? Any help is highly appreciated. Here is the picture and document I've checked.
https://docs.cloudmanager.mongodb.com/tutorial/restart-deployment/
You have application(s) that are connected to your deployment that are responsible for these connections. Identify the applications in question, then identify whether they are leaking connections and if so fix them. If your applications genuinely need more than 500 connections you need a higher tier of Atlas.
The document you located is not applicable to you. See here, cloud manager is used when you host MongoDB yourself.
I need to monitor a JDK 8 JVM on a production Red Hat 6 Linux server that allows me no direct access. I'm able to connect to the JMX port using VisualVM.
I can see the Monitor tab: CPU usage; heap and metaspace; loaded and unloaded classes; total number of threads.
However, I can't see dynamic data on the Threads tab. It shows me total number of threads and daemon threads, but no real time status information by thread name.
I don't know how to advise the owners of the server how to configure the JDK so I can see dynamic data on the Threads tab.
It works fine on my local machine. I can see the status of every thread by name, with color coded state information, if I point VisualVM to a Java process running locally.
What JVM setting makes dynamic thread data available on the JMX port?
Update:
I should point out that I'm using JBOSS 6.x.
If I look at my local JBOSS 6.x standalone.xml configuration I see the following subsystem entry for JMX:
<subsystem xmlns="urn:jboss:domain:jmx:1.3">
<expose-resolved-model/>
<expose-expression-model/>
<remoting-connector/>
</subsystem>
I can see all dynamic thread information when running on my local machine.
I'm asking the owners of the production instance if the standalone.xml includes this subsystem. I'm hoping they will say that theirs is different. If it is, perhaps modifying the XML will make the data I need available.
I'm new to Cassandra and JBoss, and am trying to create a connection pool. I've searched everywhere and found bits and pieces of information, but I'm still missing something.
I'm not clear on what I need in my standalone file, within the driver element. What should I specify for driver-class and xa-datasource-class?
And, in module..xml, what path should I be using in the resource-root element?
I have these 2 jar files - are they correct?
cassandra-driver-core-2.0.2.jar
cassandra-driver-dse-2.0.2.jar
I'm able to open a connection and execute cql queries from a standalone Java class, but now I need to create a connection pool in JBoss. Any help would be appreciated. Thanks.
Cassandra driver, itself maintains connection pool (atleast with datastax jars), which is configurable, in the run-time,
and also can be configured while making the session.
On top of that cassandra driver even lets you read connection pool status, if you have chosen to do that. So you can create your own monitoring service for connection pool status.
So, not sure, what you are trying to achieve here, pool on top of another pool?
I have 2 instances of Jboss servers running on eg: 127.0.0.1 and 127.0.0.2.
I have implemented Jboss load balancing, but am not sure how to achieve server failover. I do not have a webserver to monitor the heartbeat and hence using mod_cluster is out the question. Is there any way I can achieve failover using only the two available servers?
Any help would be appreciated. Thanks.
JBoss clustering automatically provides JNDI and EJB failover and also HTTP session replication.
If your JBoss AS nodes are in a cluster then the failover should just work.
The Documentation refers to an older version of JBoss (5.1) but it has clear descriptions of how JBoss clustering works.
You could spun up another instance to server as your domain controller, and the two instances you already have will be your hosts. Then you could go through the domain controller, and it will do the work for you. However, I haven't seen instances going down to often, it usually servers that do, and it looks like you are using just one server (i might be wrong) for both instances, so i would consider splitting it up.
did anyone tried monitoring memcached statistics with openNMS?
If you did, what did you use?
Since version 1.7.4, there'd a memcached monitor bundled with OpenNMS.