It really doesn’t matter what’s in the query. The first question to answer is whether the actual query itself is still running on the DB. if this is SQL Server, you can find out the running processing from the host of your server and see if there is actually a query running or if CF just got hung up waiting for some low level packet to come across the network (which will never arrive). These sort of issues are usually an issue with the JDBC driver itself, not CF.
Sorry, I should have been more specific. I’ve seen this happen with clustered SQL Server (master/slave) instances when the primary instance is failed over to the backup server. If you’re not using clustered SQL Servers, then disregard.
Yeah, no clue there. You haven’t provided any details about your session end error. In fact, those don’t even happen in the context of a running HTTP request.
What’s so surprising about that? You seem to have a little too much faith in the JVM’s ability to stop threads which are running native code. The rule of thumb is, any time a thread is stuck at any sort of socketRead() method, it can’t be killed. It’s just how the JVM works, love it hate it. Lucee has no control over what the JVM does or doesn’t do here. The likely only solution is to restart the JVM. But stuck threads like this generally don’t cause any issues per se (other than wasting a thread on your JVM ) so long as they don’t hold any open locks or resources.
I doubt the CF application timeout will have any affect on it. It will likely run until you restart your server.