Poll metrics failure on Docker container. about jmx2graphite HOT 11 CLOSED

Just checked that it wasn't the container by doing a source build (following the instructions given using gradlew) and get the same error message.

from jmx2graphite.

from jmx2graphite.

Unfortunately not a Java dev, but I had a go, output is
jmx2graphite.txt

from jmx2graphite.

@bluebob That was very helpful. I still have one missing piece of information. JMX2Graphite first runs an HTTP request to Jolokia to get the list of available metric beans. You can see he got it:

17/02/15 14:05:36 INFO jmx2graphite.MetricsPipeline: Found 790 metric beans. Time = 715ms, for 2017-02-15T14:05:30.000+0000

Next it run a POST request to Jolokia, in the body it writes all the metric beans he got before. The response body is supposed to be an Array of JSON object, one per metric. From some reason, the response body is a single JSON Object thus you see this exception:

Can not deserialize instance of java.util.ArrayList out of START_OBJECT token

I've pushed a commit to jmx2graphite and adds trace messages printing the request body and response body in TRACE log level.

Can you please do a git pull, build from source, set log level to TRACE, and paste back the result? Sorry for the inconvenience.

from jmx2graphite.

Sorry for delay, log file (a lot larger!) attached.
jmx2graphite112.txt

from jmx2graphite.

Weird. The response from Jolokia even though the status code is 200. I can get around that, but still Jolokia fails. What version of Jolokia are you using ?

from jmx2graphite.

Jar running claims to be "jolokia-jvm-1.3.5-agent". Host is RHEL7.2

from jmx2graphite.

@bluebob I managed to track down the bug. It's in Jolokia JVM Agent. I've opened a bug for them here: jolokia/jolokia#305.
It is caused if your JVM Agent was started in debug mode. How does your -javaagent command argument looks like?

from jmx2graphite.

Sorry for delay in replying. Sure enough the JOLOKIA_OPTS setting I was using was "--debug". I've switched that to "--verbose" and jmx2graphite seems to be working fine now. Now all I've gotta do is turn off all that trace output... :)

from jmx2graphite.

from jmx2graphite.

Oops, yes. Thanks. :)

from jmx2graphite.