Exceeding Concurrent Request Maximum Yields 200 Code and Empty Body

Description

We were going to try doing some load testing against different max concurrent request settings but I found some unexpected behavior which prevents this from being a viable option.

Expected Behavior

According to the admin, "If the time is reached the request is rejected with an exception." Therefore, with a timeout of 1 second set, I would expect to get some kind of 5xx exception, plus something in the error logs.

Actual Behavior

When the "maximal" (btw, that should be labeled "maximum") concurrent request count is exceeded, I get:

  • 200 response code

  • Empty response body

  • Nothing in any logs that I can find

Because of this, the feature is not useful to me, because I can't present an end user with a blank screen.

Environment

Lucee Docker Image

Attachments

2

Activity

Pothys - MitrahSoft 
6 September 2021 at 11:42

I've checked this ticket and confirmed the issue happened on lucee latest version 5.3.9.4-SNAPSHOT too. Admin Concurrent Requests feature, if the server reached the maximum concurrent requests and request queue timeout shows the blank page with status code 200. Seems ACF shows Service Unavailable error with status code 503.

 

Error in ACF:

Details

Assignee

Reporter

Priority

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 3 September 2021 at 21:36
Updated 6 September 2021 at 11:43