Kbase P126946: A _sqlsrv2 process starts consuming large amounts of CPU after a SQL client connection
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/03/2009 |
|
Status: Verified
SYMPTOM(s):
A SQL client hangs after connecting to the database.
The _sqlsrv2 server process that the SQL client connects to starts consuming high amounts of CPU.
The first two SQL clients connect and run, but the third SQL client hangs after connection.
All three SQL clients connect via the same server even though -Mi 1 was specified.
A secondary login broker is started (using the -m3 startup parameter), but the -ServerType parameter is not used to specify the client connection type.
Two startup parameter files (.pf) are used to start the primary and secondary login brokers.
Both startup parameter files contain -Mn, -Ma and -Mi startup parameters, but neither contain the -Mpb parameter.
FACT(s) (Environment):
Solaris
OpenEdge 10.1B
OpenEdge Category: Configuration
CAUSE:
The exact cause is unknown at the time of this writing.
FIX:
Configure the primary and secondary login brokers to use -ServerType and -Mpb to clearly separate connection types.