say I ask my database to kill all its open connections, can I inform lucee about this and ask lucee to reopen a connection for some datasource?

@David Rogers Every 60 seconds or so, Lucee will test every connection it has to see if it's still valid. if not, it will be discarded.

i have something like

queryexecute("
kill every connection to some_test_db;
-- do other stuff
", {}, {datasource: "master/i.e. not some_test_db"})

which works every other request (coinciding with the above comment it seems) (edited for marginally improved clarity)

I'm not quite clear what you're doing, but if that SQL kills any open connections, then yeah it would be an issue.

naively I'd have figured that's a driver option, c'est la vis

here is the setting

hm, what happens if the connection is dead and it doesn't validate it as dead...I guess I will find out!

I would just add that while the overhead may be minimal, if you choose to validate before each request it does add some overhead. If you're trying to force the connection for the same request, you could just manually fire off a validation query in a try/catch, which I think then on the second attempt should re-open the connection.

if you choose to validate before each request

as in, the box Brad posted is checked, yes?

hm, what happens if the connection is dead and it doesn't validate it as dead...I guess I will find out!

Huh? What do you mean? Are you saying the JDBC driver may have a bug and not work correctly?

i might not be correctly using the term/idea "connection"

if you choose to validate before each request it does add some overhead.

This is correct. I'm fairly sure the JDBC-level verification doesn't actual run any SQL, it just sends a round trip ping to the server to ensure it's still there.

you could just manually fire off a validation query in a try/catch,

While this work "work", it seems worse in every possible way 😆 It's for sure going ot be more overhead. I'd let the JDBC drivers do their thing. The validation process is actually built into the JDBC spec and lucee is simply asking the JDBC driver to check the connection to make sure it's life still.

@bdw429s I just meant if he has a specific request in which he's killing the connections, but later wants to run some queries in the same request, he could manually validate. Not that you'd want to do that on every request. Obviously, that doesn't solve issues with other running requests.

Ahh, I see what you mean-- the problem is even if only one request kills the connection, the "dead" connection object would still cause an error on whatever random request tried to use it next

oh, i'm not validating before use but should be in this case ... I thought it was the other way around ... hm, actually not sure, gotta look at my settings. this is a good intro I appreciate it gents

i'm not validating before use

To be clear, it's not an action you need to take in your code. You just check the box in the admin and you're done. Lucee does it for you when checking a connection out of the pool before it it used to execute your query. If it isn't valid, lucee discards it and takes another from the pool. Rinse and repeat until a valid connection is found, or a new one is created.

is this something that can be added to the Application.cfc datasource definition or is it only an admin/cfconfig setting?

@sknowlton It can be done in application.cfc