Thank you for the detailed explanation of your issues.
The integrated security approach is only supported when you rely on the ADO driver itself. This can be done by either choosing the 'Use Telerik Data Access Connection Pool with Telerik Data Access Connection Management
' or 'Use ADO Connection Pool'
setting as you already found out.
The reason for that is, that when using the integrated connection pool, we are managing the open connections. Though we can not take care about the actual credentials used for the actual connection since our the connection pool just manages all connections with the same string. In case of integrated security, all users are using the same connection string and can therefore not be separated.
The ADO driver instead is able to handle this situation and is therefore the way to go. With the previously mentioned settings
you are using the ADO connection pool instead of the integrated one though with the 'Use Telerik Data Access Connection Pool with Telerik Data Access Connection Management
' setting we allow some maintenance tasks on the connections to be done.
Regarding the mentioned exception 'Exception in connection pool cleanup thread'. This could be related to the problem above though we are not tracking enough information at the moment to really know what the cause here is.
That said, with the next version of the Product, to be expected in mid of April, we have enhanced the exception reporting which allows us to dig deeper here.
I hope this information is helpful for you.
Feel free to ask in case you have any other question.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map