The ADO pooling is NOT disabled in connection string, the Telerik pooling is set to use only ADO pooling with <poolType>2</poolType>
The following happens:
- if i close the remote database and then try to access the remote database again, i get the connection state as "closed", if i try to reopen it (with closed db) i get nearly immediately the correct exception that the db is closed/not accessible or that the TransactionScope is not active.
This seems to be the expected behaviour. Some warning that something occured with the connection (even it would be better to have the same warning and not different ones) and no deadlock with the Monitor.Enter.
Before the problem was occuring every time if i was just closing the database or
disconnecting the network on another computer and then directly using
Telerik to try to get an object by identifier
I don't know if this is a stable state yet, or if the problem can reoccur by some strange race condition.
What are the drawbacks of the <poolType>2</poolType> setting?
From sybase i have the following information:
> SAConnectionPoolManager can potentially have thread-safety issues if
> multiple threads are trying to allocate/close multiple connection
> This investigation has been opened as CR #730642, but has not been
> currently resolved.