Sai Vamsi,
On 11/29/23 03:50, Bodavula, Sai Vamsi Mohan Krishna (TR Technology) wrote:
I am trying to add Tomcat-JMX Integration to the Datadog Agent, in order to
achieve Remote Monitoring .
I am following the docs
https://docs.datadoghq.com/containers/guide/autodiscovery-with-jmx/?tab=helm#autodiscovery-annotations
[https://datadog-docs.imgix.net/images/dd-docs-meta-image.png]<https://docs.datadoghq.com/containers/guide/autodiscovery-with-jmx/?tab=helm#autodiscovery-annotations>
Autodiscovery with
JMX<https://docs.datadoghq.com/containers/guide/autodiscovery-with-jmx/?tab=helm#autodiscovery-annotations>
Datadog, the leading service for cloud-scale monitoring.
docs.datadoghq.com
This is the Environment I am using in my case.
I am trying to integrate JMX in one my Deployment, in AKS environment and I am
using Helm to upgrade my environment.
as suggested in the documentation., I am adding the annotations in my
deployment file in helm structure.
Okay, I know absolutely nothing about Azure, Kubernetes, or Helm. But it
looks like maybe this is more basic than that...
My agent is JMX enabled, and i can see in deployment logs.
I have configured a service for this deployment and its reflecting.
Issue I am facing :
I am trying to add my annotations, in the deployment file, after deployment,
it should be able make the remote connection , but its showing these logs in
the agent.
I will be of no help in figuring out what "annotations" you need in your
"deployment file" because - again - I know nothing about Azure, Kube,
and Helm.
while i check the Java process., even its not reflecting this JMX process , it
seems JMX process is not at all created, in my case.,
error i am facing after deployment"
========
JMXFetch
========
Information
==================
runtime_version : 11.0.18
version : 0.47.8
Initialized checks
==================
tomcat
instance_name : tomcat-10.75.12.143-1099
message : Unable to instantiate or initialize instance
10.75.12.143:1099. Is the target JMX Server or JVM running? Failed to retrieve
RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: 10.75.12.143; nested
exception is:
java.net.ConnectException: Connection refused (Connection refused)]
Well THAT seems straightforward.
First: is that the right IP address?
Second: on that server (10.75.12.143), is port 1099 bound-to by the
Tomcat process? Can you, for example, nc to that TCP/IP port? Have you
checked the Tomcat logs to see if there any errors during startup... for
example, any JMX-related errors?
Third: on that IP, is port 1099 reachable from the Helm (or whatever)
server that is trying to contact it? Try using "nc 10.75.12.143 1099"
and see if you can connect from Helm (or whatever).
- name: JAVA_OPTS
value: >-
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.port=1099
-Dcom.sun.management.jmxremote.rmi.port=1099
-Djava.rmi.server.hostname=$(POD_IP)
-Djava.net.preferIPv4Stack=true
-Dcom.sun.management.jmxremote.host=$(POD_IP)
Can you login to 10.75.12.143 and check to see if the JVM launch command
has (a) all of the above -D arguments in it and (b) if the host/hostname
have the expected values in them?
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
