InternalManagedConnectionPool.That could be the problem.
user11256882 wrote:Perhaps not for you but one can use a direct jdbc connection in a JEE container. And I suspect that you can introduce another pool as well.
It is not an option to remove the connection pooling. That is just a consequence of using a datasource.
I guess this is really a problem for the MS SQL Server JDBC team, now that it has been confirmed by someone else.I suppose if you can ignore the version of java that has the problem then it isn't a problem. If you can't and you do not have an avenue into MS that provides a possible timely fix then it would be a problem.
In our case it is not really an option to use a different driver for SQL Server,Kind of curious why that would be.
nor is it of any value to determine whether the driver works without the connection pooling since we are not using it that way.Of course the point of doing that is to localize where the problem is.
This seems to be strictly a SQL Server JDBC problem (2.0 or 3.0). It is not an issue with Oracle ojdbc14 driver, which still work with 1.6.0_29.Nor would I expect it to be. I wouldn't expect it to be a problem with the jTDS driver either. But if it was it might suggest that there is something wrong in the VM rather than the driver.
user11256882 wrote:Pretty sure I covered all of possible answers to that in my previous response.
We provide and support a product to a customer base that uses it in various operational environments that we do not control, but in which it is specified to function. What I meant was that the option to use one driver or another or one type of connection pooling or another was not in our control.