When configuring query-timeout in a WildFly datasource the singleton TimerThread class is instantiated with contextClassLoader from the first client that uses a Connection preventing garbage collect Application ClassLoader on hot redeploy the app. I think TimerThread should be initialized with library class loader as contextClassLoader to avoid that.
When configuring query-timeout in a WildFly datasource the singleton TimerThread class is instantiated with
contextClassLoaderfrom the first client that uses a Connection preventing garbage collect Application ClassLoader on hot redeploy the app. I think TimerThread should be initialized with library class loader ascontextClassLoaderto avoid that.