# Error in elastic search apm during performance testing **URL:** \ **Category:** APM\ **Created:** [August 6, 2018, 6:25pm UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202 "2018-08-06T18:25:33Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![chandra0651](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandra0651/32/30484_2.png) [@chandra0651](https://discuss.elastic.co/u/chandra0651)\ **Post date:** [August 6, 2018, 6:25pm UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/1 "2018-08-06T18:25:33Z")
Hello i installed an APM in one of my machine and started a spring boot app with apm jar to send the metrics, i am receving the data from the app correctly but when we do performance testing on the app with 1000 requests per minute my apm server is throwing below ERROR in the log file and data is not getting ingested to elasticsearch. This is only happening while doin gperformance testing do i need to change any settings in my config to handle the heavy load. > ERROR [request] beater/handlers.go:384 error handling request {"request\_id": "6cca8ddc-4d67-4b12-bdc9-6ff49ec3d263", "error": "while decoding: unexpected EOF"} ---
**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\ **Post date:** [August 6, 2018, 6:42pm UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/2 "2018-08-06T18:42:24Z")
Hi and thanks for trying out Elastic APM! Are you using the Java agent? The version 0.6.0 contains a bug which only occurs when the application is under some stress. I’ll release a bug fix ASAP. In the mean time, you can try a current snapshot: [https://github.com/elastic/apm-agent-java/blob/master/README.md#snapshots](https://github.com/elastic/apm-agent-java/blob/master/README.md#snapshots) ---
**Author:** ![chandra0651](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandra0651/32/30484_2.png) [@chandra0651](https://discuss.elastic.co/u/chandra0651)\ **Post date:** [August 6, 2018, 6:49pm UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/3 "2018-08-06T18:49:28Z")
Yes i am using the java agent version 0.6.0 ---
**Author:** ![chandra0651](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandra0651/32/30484_2.png) [@chandra0651](https://discuss.elastic.co/u/chandra0651)\ **Post date:** [August 6, 2018, 7:07pm UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/4 "2018-08-06T19:07:27Z")
Hi Felix is there any expected date when this bug is going to be fixed in the new version ---
**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\ **Post date:** [August 6, 2018, 7:09pm UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/5 "2018-08-06T19:09:47Z")
Did the snapshot work for you? I’ll release a bug fix this week. ---
**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\ **Post date:** [August 6, 2018, 7:11pm UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/6 "2018-08-06T19:11:35Z")
This is a direct link to the snapshot: [https://oss.sonatype.org/content/repositories/snapshots/co/elastic/apm/elastic-apm-agent/0.7.0-SNAPSHOT/elastic-apm-agent-0.7.0-20180806.093124-36.jar](https://oss.sonatype.org/content/repositories/snapshots/co/elastic/apm/elastic-apm-agent/0.7.0-SNAPSHOT/elastic-apm-agent-0.7.0-20180806.093124-36.jar) ---
**Author:** ![felixbarny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felixbarny/32/27341_2.png) [@felixbarny](https://discuss.elastic.co/u/felixbarny)\ **Post date:** [August 7, 2018, 11:41am UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/7 "2018-08-07T11:41:14Z")
I have released 0.6.1 with a fix for this ---
**Author:** ![chandra0651](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandra0651/32/30484_2.png) [@chandra0651](https://discuss.elastic.co/u/chandra0651)\ **Post date:** [August 13, 2018, 8:12pm UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/8 "2018-08-13T20:12:46Z")
@felixbarny this fix solved the problem thanks ---
**Author:** ![RaulMartinez](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@RaulMartinez](https://discuss.elastic.co/u/RaulMartinez)\ **Post date:** [August 27, 2018, 10:52am UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/9 "2018-08-27T10:52:36Z")
Hi Felix, I have the same problem, but in my case with normal usage, not under heavy load. It occurs when the payload has more than 1 element, **OK** 2018-08-27 12:47:40.587 [apm-reporter] DEBUG co.elastic.apm.report.ApmServerHttpPayloadSender - Sending payload with 1 elements to APM server [http://sapelk00.bsh.corp.bshg.com:8200](http://sapelk00.bsh.corp.bshg.com:8200) 2018-08-27 12:47:40.591 [apm-reporter] DEBUG co.elastic.apm.report.ApmServerHttpPayloadSender - _ **APM server responded with status code 202** _ **KO** 2018-08-27 12:48:53.587 [apm-reporter] DEBUG co.elastic.apm.report.ApmServerHttpPayloadSender - Sending payload with 8 elements to APM server [http://sapelk00.bsh.corp.bshg.com:8200](http://sapelk00.bsh.corp.bshg.com:8200) 2018-08-27 12:48:53.590 [apm-reporter] DEBUG co.elastic.apm.report.ApmServerHttpPayloadSender - **_APM server responded with status code 400_** 2018-08-27 12:48:53.591 [apm-reporter] DEBUG co.elastic.apm.report.ApmServerHttpPayloadSender - data decoding error: unexpected EOF I tried with versions 0.6.0 0.6.2 and the snapshot 0.7.0-20180827.093505-60 with no luck. I'm using apm-server version 6.3.2 Log in server side 2018-08-27T12:27:26.179+0200 ERROR [request] beater/handlers.go:414 error handling request {"request\_id": "34a774a7-b5f7-4b64-bbd6-4bd9b6336e28", "method": "POST", "URL": "/v1/transactions", "content\_length": -1, "remote\_address": "10.129.14.61", "user-agent": "apm-agent-java unknown", "response\_code": 400, "error": " **_data decoding error: unexpected EOF_**"} Any help would be appreciated! 🙂 Thanks in advance, Raul ---
**Author:** ![RaulMartinez](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@RaulMartinez](https://discuss.elastic.co/u/RaulMartinez)\ **Post date:** [August 27, 2018, 11:23am UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/10 "2018-08-27T11:23:38Z")
Hi again, Forget it. Value of jar to be loaded was not properly changed, and the same jar (0.6.0) was used in all cases. It's working now with version 0.6.2. BR, Raul ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 17, 2018, 7:23am UTC](https://discuss.elastic.co/t/error-in-elastic-search-apm-during-performance-testing/143202/11 "2018-09-17T07:23:43Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.