Details
Assignee
Michael OffnerMichael OffnerReporter
Andrew DixonAndrew DixonPriority
BlockerNew 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
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Andrew Dixon
Andrew Dixon
Priority
BlockerNew 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 2 January 2020 at 11:02
Updated 13 January 2020 at 15:33
When using Memcached for session storage, if the connection to the server(s) fails in the "Socket connection timeout" specified, Lucee just proceeds with the request and doesn't error or report this connection failure anywhere. This simply causes all requests to the server to be delayed by the timeout specified, default 3 seconds, and presumably means that local in-memory session storage is used instead (not verified).
If a connection to the Memcached server(s) cannot be made, then Lucee should report this by throwing an error.