UnmarshalException when connecting to Bamboo about jmx_exporter HOT 5 CLOSED

Hmm, this is likely a bug on the bamboo side. We should be resilient to such things, can you try adding the UnmarshalException to the list in doScrape()? If you turn on FINE logging, then we can figure out which bean and attribute is the problem.

from jmx_exporter.

Okay. I didn't know how to enable the FINE logging, so I just changed to log SEVERE. The output looked like this:

Apr 17, 2015 6:06:12 AM io.prometheus.jmx.JmxScraper logScrape
SEVERE: scrape: 'Catalina{j2eeType=WebModule, name=//localhost/, J2EEApplication=none, J2EEServer=none}aliases': null
java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
...
Apr 17, 2015 6:06:16 AM io.prometheus.jmx.JmxScraper logScrape
SEVERE: scrape: 'Catalina:j2eeType=Filter,name=accessLogFilter,WebModule=//localhost/,J2EEApplication=none,J2EEServer=none'_'modelerType': process

I guess the line above the stack trace is the culprit?

from jmx_exporter.

I'd presume so, I can't help much with debugging from here. If you could send on a PR with the exception change, I'll merge it in.

from jmx_exporter.

Thanks for the patch, can this be closed off now?

from jmx_exporter.

Yep! Thank you :)

On Thu, Apr 23, 2015 at 6:53 PM, Brian Brazil [email protected]
wrote:

Thanks for the patch, can this be closed off now?

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

from jmx_exporter.