Datasource configuration question: What is the "connection timeout" for? I understand the "connection idle timeout" but not the "connection timeout," when looking at both its and the idle timeout's descriptions.

what flavour of DB, @jamiejackson

i believe the connection timeout governs how long to wait from when a command is executed to when the response is received back to the application

that sounds right to me ⬆️ connection timeout = time limit for active connection connection idle timeout = time limit to keep connection alive after the last time it was active (can affect load/performance)

I don't believe any of these answers are entirely correct. • connection timeout is usually how long the JDBC driver waits while establishing the initial connection to the server (before any query is run) This is managed by the JDBC driver's underlying TCP management. • idle timeout, is how long a pooled connection will set in the pool before being closed and removed for lack of use. This is managed by the connection pooling in Lucee itself. • I don't think Lucee has any top level settings for actual query timeouts that apply to the running of a statement. This is driver specific and not all drivers support such a feature. That said, at one point Lucee used to detect which drivers supported a query timeout, and would set it equal to the remaining request timeout for the page. So for example, if your request time out was 30 seconds, and after 10 seconds had elapsed, you started a query, the query timeout sent to the JDBC driver would be 20 seconds (the remaining about of time left for the request)

@bdw429s, your guess (bullet 3) is the same as my interpretation #1. The JDBC URI I've been using:

jdbc:mysql://${DB_PRIMARY_HOST}:3306/${DB_PRIMARY_SCHEMA}?connectTimeout=10000&socketTimeout=120000&enablePacketDebug=true

• My connectTimeout (time to establish connection) is generous at 10s. • My socketTimeout limits query execution to 2m. I'd like to suggest description changes to the Lucee admin/docs (the docs don't mention the configs at all, or at least I couldn't find them) but I'm not even 100% clear I know which timeout Lucee's

connectTimeout

actually represents.

chatGpt had this to say

In Lucee, the Connection Timeout setting in the administrator panel controls how long Lucee waits when trying to establish a connection to an external resource, such as a database, SMTP server, or web service, before it times out and considers the attempt to have failed.

It sets a time limit for the initial connection phase. If the external resource does not respond or acknowledge the connection attempt within this timeframe, Lucee will terminate the attempt and throw an error.

I wouldn't believe anything ChatGPT has to say on the matter, lol

Although I lean toward agreeing with that particular hallucination.

Great research. That setting sounds really dumb, lol

I may have vague (and very old) memories of connections getting clogged but I think maybe I addressed that with this stuff:

?connectTimeout=10000&socketTimeout=120000