Question
· Mar 25, 2019

Service Unavailable from CSP Gateway + IIS

We recently registered unavailability of the Web service in some moments. The application goes offline.

Analyzing the IIS logs and logs in "C:\Windows\System32\LogFiles\HTTPERR" I found nothing relevant.

Analyzing the CSP Gateway logs I noticed the following behavior when unavailability occurs:

>>> Time: Tue Mar 19 09:35:12 2019; RT Build: 1701.1606aa (win64/iis); Log-Level: 0; Gateway-PID: 3536; Gateway-TID: 6020
    Initialization
    The CSP Gateway module 'C:\Inetpub\CSPGateway\CSPms.dll' is loaded  (IPv6 Enabled; MAX_CONNECTIONS=1024; MAX_SERVERS=10; MAX_APPLICATIONS=10; MAX_RESPONSE_BUFFER_SIZE=128000; Connection_Allocation=First Free; Nagle_Algorithm=Disabled; SHM=OS; IPC=WNP)
>>> Time: Tue Mar 19 09:35:12 2019; RT Build: 1701.1606aa (win64/iis); Log-Level: 0; Gateway-PID: 3536; Gateway-TID: 6316
    Initialization
    Windows Sockets library loaded (WS2_32.DLL) Version: 2.2
>>> Time: Tue Mar 19 09:35:27 2019; RT Build: 1701.1606aa (win64/iis/mod:srv=8.5); Log-Level: 0; Gateway-PID: 3536; Gateway-TID: 7224
    Error Condition
    Exception caught in f:csp: c0000005:4600
>>> Time: Tue Mar 19 09:35:27 2019; RT Build: 1701.1606aa (win64/iis/mod:srv=8.5); Log-Level: 0; Gateway-PID: 3536; Gateway-TID: 5348
    Error Condition
    Exception caught in f:csp: c0000005:4600
>>> Time: Tue Mar 19 09:35:27 2019; RT Build: 1701.1606aa (win64/iis/mod:srv=8.5); Log-Level: 0; Gateway-PID: 3536; Gateway-TID: 8836
    Error Condition
    Exception caught in f:csp: c0000005:4600
>>> Time: Tue Mar 19 09:35:27 2019; RT Build: 1701.1606aa (win64/iis/mod:srv=8.5); Log-Level: 0; Gateway-PID: 3536; Gateway-TID: 8928
    Error Condition
    Exception caught in f:csp: c0000005:4600
>>> Time: Tue Mar 19 09:35:27 2019; RT Build: 1701.1606aa (win64/iis/mod:srv=8.5); Log-Level: 0; Gateway-PID: 3536; Gateway-TID: 3736
    Error Condition
    Exception caught in f:csp: c0000005:4600
>>> Time: Tue Mar 19 09:37:46 2019; RT Build: 1701.1606aa (win64/iis/mod:srv=8.5); Log-Level: -1; Gateway-PID: 3536; Gateway-TID: 7308; Connection-No: 4; Server: csp; Cache-PID: 7196; Request-ID: 5; Session-ID: 5ELPK6TnFh; Remote-Addr: xxx.xxx.xxx.xxx; Page: GET /csp/erp/system/lib/filtro.csp
    Error Condition
    CSP application closed the connection before sending a complete response

>>> Time: Wed Mar 20 14:39:28 2019; RT Build: 1701.1606aa (win64/iis); Log-Level: 0; Gateway-PID: 4540; Gateway-TID: 2312
    Initialization
    The CSP Gateway module 'C:\Inetpub\CSPGateway\CSPms.dll' is loaded  (IPv6 Enabled; MAX_CONNECTIONS=1024; MAX_SERVERS=10; MAX_APPLICATIONS=10; MAX_RESPONSE_BUFFER_SIZE=128000; Connection_Allocation=First Free; Nagle_Algorithm=Disabled; SHM=OS; IPC=WNP)
>>> Time: Wed Mar 20 14:39:28 2019; RT Build: 1701.1606aa (win64/iis); Log-Level: 0; Gateway-PID: 4540; Gateway-TID: 6620
    Initialization
    Windows Sockets library loaded (WS2_32.DLL) Version: 2.2
>>> Time: Wed Mar 20 14:39:29 2019; RT Build: 1701.1606aa (win64/iis/mod:srv=8.5); Log-Level: 0; Gateway-PID: 4540; Gateway-TID: 5384
    Configuration Error: Insufficient space in the configuration buffer
    Configuration block Size: 126397; Size of configuration block to insert: 55114; Space available: 68611 (Consider setting CONFIG_BUFFER_SIZE=112K (or higher) in the [SYSTEM] section of CSP.ini)
>>> Time: Wed Mar 20 14:42:22 2019; RT Build: 1701.1606aa (win64/iis/mod:srv=8.5); Log-Level: -1; Gateway-PID: 4540; Gateway-TID: 5384; Connection-No: 5; Server: csp; Cache-PID: 3864; Request-ID: 6; Session-ID: OQGM5Lp1Sw; Remote-Addr: xxx.xxx.xxx.xxx; Page: GET /csp/erp/system/lib-np/js/menu/menuCtrl.js
    Error Condition
    CSP application closed the connection before sending a complete response
>>> Time: Wed Mar 20 14:43:33 2019; RT Build: 1701.1606aa (win64/iis/mod:srv=8.5); Log-Level: 0; Gateway-PID: 4540; Gateway-TID: 5912; Connection-No: ; Request-ID: 20f; Session-ID: bTpfnzY1EW; Remote-Addr: xxx.xxx.xxx.xxx; Page: GET /csp/erp/system/modulos/spd/cads/spd001.csp
    Diagnostic
    Failed to connect to 'csp' - Reason: -8 (Server busy: Gateway's configured limits exceeded) (No Retry)

We are using the versions:

Caché 2017.1.3
CSPGateway 2017.1.0.792.0
IIS: 6.2 (Windows Server 2012 R2)

 

Has anyone ever had this same problem? or do you know what it can be?


Is there any more detailed documentation of configurations between CSP Gateway and IIS?

Discussion (1)1
Log in or sign up to continue

Lucas,

Log that you provided spans from March 19th 09:35 to March 20th 14:43.

Depending on moments when application was unavailable you need to look in different records of csp.log

For example,

1) Exception caught in f:csp: c0000005:4600
c0000005 is the code for an access violation.

I would advise to you to try installing latest release version of CSP Gateway, or if this error still appears there, contact InterSystems Worldwide Response Center to fix this error.

2) CSP application closed the connection before sending a complete response

This is most likely something with the code of the page "/csp/erp/system/lib/filtro.csp". It started to write some answer back and then closed the connection, for example process terminated itself with halt

3) Configuration Error: Insufficient space in the configuration buffer
Configuration block Size: 126397; Size of configuration block to insert: 55114; Space available: 68611 (Consider setting CONFIG_BUFFER_SIZE=112K (or higher) in the [SYSTEM] section of CSP.ini)

This message is self-explanatory

4) Failed to connect to 'csp' - Reason: -8 (Server busy: Gateway's configured limits exceeded) (No Retry)

CSP Gateway can limit number of total connections to server and connections per session that it makes to Caché. See parameters "Maximum Server Connections" and "Maximum Connections per Session" here.

Generally for IIS-specifics read section "Microsoft IIS All Versions" of CSP Gateway configuration guide. And for general configuration of CSP Gateway -- chapter "CSP Gateway Operation and Configuration".