Normally everything is working fine, but every time Oracle is recycled for maintenance or patches, we get this error, coming from a BizTalk 2016 SendPort:
Error Description: Microsoft.ServiceModel.Channels.Common.ConnectionException: Connection request timed out ---> Oracle.DataAccess.Client.OracleException: Connection request timed out
Our current "get around" is to recycle the BizTalk Host Instance, but as this can occur on off hours and weekends, that is not an ideal situation, better to somehow avoid the error altogether.
The SendPort has this property: UseOracleConnectionPool = True, which according to this page:
ODP.NET property. Specifies whether to use the ODP.NET connection pool. The default is True, which enables connection pooling. The Oracle Database adapter implements connection pooling by using the ODP.NET connection pool.
So I would like to know if setting this parm to False might avoid this error (at the cost of slower connections). Of course we can test it, but it takes a team of a few people to set it up, recycle Oracle, and try it again. (I'm not yet sure which release of Oracle it is.)