Kbase P154292: Getting error "Broker rejects connection" when connecting ODBC client to database broker on Windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/13/2009 |
|
Status: Unverified
SYMPTOM(s):
Getting error "Broker rejects connection" when connecting ODBC client to database broker on Windows when broker was started with large amount of shared memory.
Cannot connect with ODBC
Using large values for -B and -L on Windows system.
Copy of the database can be started with AdminServer and SQL connections are possible.
Broker rejects connection
Using identical startup parameters for copy of database prevents SQL servers from spawning on copy of database.
[2009/10/13@16:08:55.417-0400] P-3764 T-3768 I BROKER 1: (796) Error writing msg, socket=6296 errno=10054 usernum=1 disconnected.
[2009/10/13@16:09:37.634-0400] P-2952 T-5920 I SQLSRV2 50: (-----) SQL Server 10.1C.03 started, configuration: "foo.db.virtualconfig2"
[2009/10/13@16:09:37.634-0400] P-2952 T-5920 I SQLSRV2 50: (-----) Failure during dsmUserConnect (-1)
[2009/10/13@16:09:37.634-0400] P-2952 T-5920 I SQLSRV2 50: (-----) Failure during dsmShutdownUser (-1). Proceeding.
FACT(s) (Environment):
Windows Server 2003
OpenEdge 10.1C
ABL / 4GL servers start without error.
CHANGE:
Migrated from version 9 to 10.1C
CAUSE:
The amount of shared memory created by the database broker based on the startup parameters have exceeded the permissible size for some connections in shared memory.
FIX:
Review values defined for such parameters as -B; -Mxs, and -L.
If any definition for -tablebase; -tablerangesize; -indexbase or -indexrangesize are listed as startup parameters then these will use additional memory by the broker to reserve space for the structures to hold data for all the tables and indices reflected by these parameters.
Reduction of the total amount of memory used by the broker will be necessary to allow the shared memory connection that is failing.