32 bit Unmanaged ODP.NET client. Connection string is only specifying Pooling=true, no other pool settings are being set, such that the defaults should be being used. Connecting to an Oracle 12 exadata db.
When TraceLevel set to 2, as shown by the TRC snippet below. Ff I am reading this correctly, the highest it got was 49-51 connections and then the errors start for all users. If the default "Max Pool Size" is 100, why wouldn't the trace be showing that the oracle client should be reaching that point before having difficulty? Restarting IIS resolves the issue. Connections are being disposed appropriately.
--inst={blanked}: tot=49; used=49; idle=0--
CPU/memory is not impacted during these errors.
Is there a server based configuration that could be limiting the allowed connections by an oracle client?
Other customer implementation (non-exadata) are not demonstrating this issue.
Snippet of the log:
TIME:2021/08/24-10:10:35:309 TID:27e0 OpsConIsACEnabled(): OCI_ATTR_FO_TYPE on the Connection: 2
TIME:2021/08/24-10:10:35:515 TID:27e0 (POOL) ConnectionPool::PutConnection: (A) Pushed onto the Stack, StackCount: 1
TIME:2021/08/24-10:10:35:649 TID:26c4 (ENTRY) GetConnectionPool()
TIME:2021/08/24-10:10:35:649 TID:26c4 (POOL) (AFFINITY) (Dispensed con for {blanked}; no affinity specified
TIME:2021/08/24-10:10:35:649 TID:26c4 (POOL) (AFFINITY) (inst={blanked}: tot=49; used=49; idle=0)
TIME:2021/08/24-10:10:35:649 TID:26c4 OpsConIsACEnabled(): OCI_ATTR_FO_TYPE on the Connection: 2