Internal Server Error (500 status code) with message "No message available"

[apibugsreporting]

Bug Description

I found a request obtaining a 500 status code with the error message "No message available". The 500 status code is reproducible, but the message is not (now the message is "Index 0 out of bounds for length 0"). However, I have a test report showing the "No message available" error message (see link at the end of the bug report).

General Information

Please include the following general information about the issue and list any additional steps needed to reproduce the bug.

• Version of the ohsome API [e.g. 1.5.0]
  • 1.6.1
• Which API instance was requested [e.g. remote instance at https://api.ohsome.org/v1, local instance with an h2 file or connected to the cluster, etc.]
  • Remote instance at https://api.ohsome.org/v1
• Affected endpoint(s) [e.g. /contributions/count]
  • /elements/count/density/groupBy/boundary/groupBy/tag
• URL of your request (and request body if applicable)
  • https://api.ohsome.org/v1/elements/count/density/groupBy/boundary/groupBy/tag?filter=bicycle%3D*%20and%20not%20geometry%3Aline%20and%20id%3A%281%20..%209999%29&groupByKey=highway&format=geojson&time=2011-10-13&timeout=99&bcircles=8.70491%2C49.40631%2C85%7C8.708%2C49.411%2C3%7C8.7493%2C49.434%2C48
• Used HTTP method [GET or POST]
  • GET
• Utilized tool/library for the request [e.g. cURL, Postman, ohsome-py, etc.]
  • RESTest

Expected Behaviour

A 500 status code (Internal Server Error) should not be returned. There is probably some uncaught exception in the code.

Further Information

Additional Information

A test report revealing this issue is available at the following URL (it might take some time to load):

• http://apitesting.ddns.net/fse2022/restest/target/allure-reports/ohsome__r_cbt_custom/#categories/882a17760bce9dccc99edbd9f7e59f35/ecb286a3c5503006/