Is it possible to close all incoming JDBC connections using VQL statements? Or is there another command I can use to kill/close all incoming JDBC connections?
Here's why I'm asking:
1) When I run deployments, my script automatically removes a denodo server from the F5 pool. (Our pool is configured to load balance incoming requests on port 9999 and 9090)
2) When I perform step 1, I've noticed that new, incoming http requests on port 9090 are automatically picked up by the servers that are left in the pool (no news here).
3) I've also noticed that NEW JDBC requests on port 9999 are automatically picked up by the servers that are left in the pool (no news here)
4) Unfortunately, I've noticed that existing JDBC connections to the server I removed from the F5 pool are NOT automatically closed... so I'm trying to figure out how I can easily close all JDBC connections WITHOUT restarting the VQL Server.
Thus my question... how can I kill/close all incoming JDBC connections to make sure NO queries are run against my server while it is not part of the F5 pool?
(And please don't say JMX :-) . The scripting language I'm using doesn't really work with JMX, so I'd have to write a wrapper around the JMX system to make it easy to call from the linux command line)