Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cast for new jmxfetch #777

Closed
ive opened this issue Dec 25, 2013 · 1 comment
Closed

Cast for new jmxfetch #777

ive opened this issue Dec 25, 2013 · 1 comment
Milestone

Comments

@ive
Copy link

ive commented Dec 25, 2013

In current dadadog 4.x version if yaml (for example tomcat) has option port: set as "12345" (note " instead of just pure number), datadog read config, start jmxfetch but
$datadog-agent info shows
Unexpected exception while initiating instance localhost:11198 : java.lang.String cannot be cast to java.lang.Integer
java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer
at org.datadog.jmxfetch.Connection.(Connection.java:49)
at org.datadog.jmxfetch.ConnectionManager.getConnection(ConnectionManager.java:43)
at org.datadog.jmxfetch.Instance.init(Instance.java:81)
at org.datadog.jmxfetch.App.init(App.java:298)
at org.datadog.jmxfetch.App.init(App.java:208)
at org.datadog.jmxfetch.App.main(App.java:53)

Previous version behave differently. It seems wize to try casting port to int() or log error\warning.

@remh
Copy link
Contributor

remh commented Feb 10, 2014

Closed in favor of:
DataDog/jmxfetch#16

@remh remh closed this as completed Feb 10, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants