Feedback
Did this article resolve your question/issue?

   

Article

OpenAccess JDBC driver takes long time to close the connection

Information

 
TitleOpenAccess JDBC driver takes long time to close the connection
URL NameOpenAccess-JDBC-driver-takes-long-time-to-close-the-connection
Article Number000112976
EnvironmentProduct: OpenAccess JDBC Client
Version: 7.2, 8.1
OS: Windows
Database: N/A
Application: All supported applications
Question/Problem Description
Closing a connection with OpenAccess JDBC client takes more than 30 seconds as it does not send the TCP FIN to close the session after close_notify.
Steps to Reproduce
Clarifying Information
Error Message
Defect NumberDefect OASL-210
Enhancement Number
Cause
When the client (JDBC driver) is closing the connection, it sends the SSL close_notify, but does not close the TCP session with a TCP FIN.
Resolution
Fixed in hot fix 8.1.0.0085.
Refer to "OpenAccess SDK hot fix download and install instructions" for instructions on how to download and install the hot fix.

Hidden connection option was needed to implement this fix. Please contact support for details.
Workaround
Notes
Last Modified Date11/20/2020 7:01 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.