# Internal Server Error on JVM instance metrics **URL:** \ **Category:** APM\ **Tags:** ui\ **Created:** [March 25, 2020, 2:16pm UTC](https://discuss.elastic.co/t/internal-server-error-on-jvm-instance-metrics/224998 "2020-03-25T14:16:47Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Harm](https://avatars.discourse-cdn.com/v4/letter/h/b4bc9f/32.png) [@Harm](https://discuss.elastic.co/u/Harm)\ **Post date:** [March 25, 2020, 2:16pm UTC](https://discuss.elastic.co/t/internal-server-error-on-jvm-instance-metrics/224998/1 "2020-03-25T14:16:47Z")
**Kibana version** : 7.6.0 **Elasticsearch version** : 7.6.0 **APM Server version** : 7.6.0 **APM Agent language and version** : Java 1.12-1 **Browser version** : Chrome 80.0.3987.149 **Original install method (e.g. download page, yum, deb, from source, etc.) and version**: Kibana from Elastic Cloud, Java agent from Maven, APM-server via .deb **Fresh install or upgraded from other version?** Upgrade from 7.4.0 **Is there anything special in your setup?** - **Description of the problem including expected versus actual behavior** : When opening the JVM instance metrics for any of our JAVA services, an error pops-up with: Error while fetching resource. Error: Internal Server Error (500). The page does seem to load fine. But I see that the backend-call to /metadata is failing with response: {"statusCode":500,"error":"Internal Server Error","message":"An internal server error occurred."} **Steps to reproduce** : 1. Open APM in Kibana 2. Select a JAVA service 3. Click on JVMs 4. Select a JVM instance **Errors in browser console (if relevant)**: GET [https://our.domain/api/apm/services/java-service/node/node-01/metadata?start=2020-03-24T14%3A15%3A10.008Z&end=2020-03-25T14%3A15%3A10.009Z&uiFilters={}](https://our.domain/api/apm/services/java-service/node/node-01/metadata?start=2020-03-24T14%3A15%3A10.008Z&end=2020-03-25T14%3A15%3A10.009Z&uiFilters=%7B%7D) 500 (Internal Server Error) **Provide logs and/or server output (if relevant)**: Not available unfortunately. Kibana is running from Elastic Cloud. ---
**Author:** ![dgieselaar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dgieselaar/32/46947_2.png) [@dgieselaar](https://discuss.elastic.co/u/dgieselaar)\ **Post date:** [March 27, 2020, 10:42am UTC](https://discuss.elastic.co/t/internal-server-error-on-jvm-instance-metrics/224998/2 "2020-03-27T10:42:31Z")
> [@Harm](#): > > /api/apm/services/java-service/node/node-01/metadata?start=2020-03-24T14%3A15%3A10.008Z&end=2020-03-25T14%3A15%3A10.009Z&uiFilters={} Hi @Harm, this could be the result of a bug we had in 7.6 and which will be fixed in 7.7. We display some metadata (host.hostname and container.id) above the charts. If there are no documents that have (both) these fields set, the request for the metadata will fail. Does that sound like it applies to your data? ---
**Author:** ![Harm](https://avatars.discourse-cdn.com/v4/letter/h/b4bc9f/32.png) [@Harm](https://discuss.elastic.co/u/Harm)\ **Post date:** [March 27, 2020, 3:30pm UTC](https://discuss.elastic.co/t/internal-server-error-on-jvm-instance-metrics/224998/3 "2020-03-27T15:30:05Z")
@dgieselaar, thanks for your reply. The field container.id isn't set in any of our documents. If I understand you correctly that will cause this error to appear? If so, I'll patiently wait for the 7.7 release.. 🙂 ---
**Author:** ![dgieselaar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dgieselaar/32/46947_2.png) [@dgieselaar](https://discuss.elastic.co/u/dgieselaar)\ **Post date:** [March 27, 2020, 9:03pm UTC](https://discuss.elastic.co/t/internal-server-error-on-jvm-instance-metrics/224998/4 "2020-03-27T21:03:01Z")
Yep, that's correct! It's probably a little annoying to have it pop up, but everything else should work correctly. Let me know if you still see issues after upgrading to 7.7 (when it comes out). ---
**Author:** ![dgieselaar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dgieselaar/32/46947_2.png) [@dgieselaar](https://discuss.elastic.co/u/dgieselaar)\ **Post date:** [March 30, 2020, 12:47pm UTC](https://discuss.elastic.co/t/internal-server-error-on-jvm-instance-metrics/224998/5 "2020-03-30T12:47:07Z")
@Harm Need to correct myself here, the fix was also backported to 7.6.1., so you should be able to use that version as well. ---
**Author:** ![Harm](https://avatars.discourse-cdn.com/v4/letter/h/b4bc9f/32.png) [@Harm](https://discuss.elastic.co/u/Harm)\ **Post date:** [March 30, 2020, 2:14pm UTC](https://discuss.elastic.co/t/internal-server-error-on-jvm-instance-metrics/224998/6 "2020-03-30T14:14:31Z")
Hi @dgieselaar. thanks for the update. I just upgraded to 7.6.1 and it got fixed indeed. 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 20, 2020, 10:14am UTC](https://discuss.elastic.co/t/internal-server-error-on-jvm-instance-metrics/224998/7 "2020-04-20T10:14:32Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.