Feedback
Did this article resolve your question/issue?

   

Article

_sqlsrv2 processes persist on OpenEdge database machine when HDP server is shutdown

Information

 
Title_sqlsrv2 processes persist on OpenEdge database machine when HDP server is shutdown
URL Namesqlsrv2-processes-persist-on-OpenEdge-database-machine-when-HDP-server-is-shutdown
Article Number000123328
EnvironmentProduct: Hybrid Data Pipeline (HDP)
Version 4.6.1
OS: All supported platforms
Database: OpenEdge
Application: N/A
Question/Problem Description
Why do the _sqlsrv2 processes persist on the OpenEdge Database machine when HDP server shutdown?
Steps to Reproduce
Clarifying Information
OData Connections are being made from HDP to OpenEdge.
If the HDP server is shutdown for maintenance by running the stop script, the connections remain open on the OpenEdge machine. _sqlsrv2 processes persist and do  not go away.
User is manually killing the _sqlsrv2 processes on the database.
Error Message
Defect Number
Enhancement Number
Cause
This is expected product behavior.
Resolution
It is completely normal for the _sqlsrv2 processes to persist after the HDP server is stopped.
Once a server process is started, in this case _sqlsrv2, it is allowed to persist so future connections do not experience the delay that occurs when spawning a new server.
 
Workaround
Notes
Last Modified Date11/20/2020 6:55 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.