Go to All Forums

NumberFormatException on agent log

I see this exception in agent logs, seems like it's trying to parse a string to a number and getting an exception.

java.lang.NumberFormatException: For input string: "5432,wifi-prod-vm2:5432"

5432 must be postgresql port but I don't where the agent reads that "5432,wifi-prod-vm2:5432" string.
Here is the whole exception.



[05 Aug 2015 13:11:00][TrackerProcessor][INFO]: SQL: SELECT version();
[05 Aug 2015 13:11:02][agentsc-1-thread-1][WARNING]: [MetricDataDispatcher] Exception
java.lang.NumberFormatException: For input string: "5432,wifi-prod-vm2:5432"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
        at java.lang.Integer.parseInt(Integer.java:580)
        at java.lang.Integer.parseInt(Integer.java:615)
        at com.manageengine.apminsight.agent.util.InetAddressUtil.getPort(InetAddressUtil.java:75)
        at com.manageengine.apminsight.agent.metrics.ComponentMetric.getComponentWagesDataInMap(ComponentMetric.java:86)
        at com.manageengine.apminsight.agent.metrics.ApdexMetric.getDataInList(ApdexMetric.java:144)
        at com.manageengine.apminsight.agent.metrics.ApdexMetric.toString(ApdexMetric.java:150)
        at java.lang.String.valueOf(String.java:2979)
        at java.lang.StringBuilder.append(StringBuilder.java:131)
        at com.manageengine.apminsight.agent.metrics.Metric.toString(Metric.java:69)
        at java.lang.String.valueOf(String.java:2979)
        at java.lang.StringBuilder.append(StringBuilder.java:131)
        at java.util.AbstractMap.toString(AbstractMap.java:536)
        at java.lang.String.valueOf(String.java:2979)
        at java.lang.StringBuilder.append(StringBuilder.java:131)
        at com.manageengine.apminsight.agent.metrics.store.AbstractMetricStore.getAllMetrics(AbstractMetricStore.java:223)
        at com.manageengine.apminsight.agent.metrics.data.transport.MetricDataDispatcher.dispatchMetrics(MetricDataDispatcher.java:79)
        at com.manageengine.apminsight.agent.metrics.data.transport.MetricDataDispatcher.run(MetricDataDispatcher.java:62)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)



Thanks
Yalim Aytul


Relates to support ticket #90776
Like (1) Reply
Replies (1)

Hi Yalim Aytul,

Thank you for raising this issue. Our sincere apologies for the inconvenience. We have sent you the patched agent jar through support. And the fix will be rolled out in our next update in a day or 2.

Please let us know, if you still face any issue.

Regards,
Raji.





Like (0) Reply

Was this post helpful?