Have a question related to the scenario When connecting from a Java application using the Microsoft JDBC Driver 4.0 to a SQL Server 2014 with AlwaysOn Availability Groups set up for high availability. With this set up, we will be connecting to an availability group listener (specified in the db connecting string instead of any particular instance), so that the DB failover etc is handled gracefully by the listener and it tries to connect to the next available instance behind the scenes if current primary goes down in the AG cluster.
Question I have is, the datasource that is configured on the j2ee application server side (we use WebSphere), what happens to those connections already pooled by the datasource ? when a database goes down, though the AG listener would try to reconnect on the db side to the next available DB , will the AG Listener through the jdbc driver send an event or something to the datasource created on the app server and make sure those connections that are already pooled by the datasource to be discarded and have it create new ones so that transactions on the application side wont fail (though they might for a while till new connections are created and fail over is successful) or the java application has to find out only after requesting it from the datasource ?
basically wanted to know what happens to the already pooled connections by a datasource in the above scenario and is there any setting recommended to be set on the datasource for these type of situations please suggest?