connection terminated abnormally; client socket shut down

[Former Member]

Hello,

We have a few agents running 24/7. Several customers are having the same setup, but slightly different machines / OS or even SQL Anywhere (not prior to version 12).

At this site every night the agents loose the connection to the DataBase. But i cannot figure out whether this is a caused by the DataBase the Application. It seems to me the application looses the connection, but i am not sure.

Can you point me in the right direction. Googling gives me too much info:-)

Regards,

Marc

from database console
---------------------
I. 11/22 00:26:04. Cache size adjusted to 4251432K
I. 11/22 00:26:55. Connection ID 24034: connection "usr" terminated abnormally; client socket shut down
I. 11/22 00:26:55. Connection ID 24034: Disconnected TCPIP client's AppInfo is IP=192.168.96.38;HOST=BG-NLEDI;OSUSER=perry.myname;OS='Windows 2012R2 Build 9200 ';EXE=C:\\apps\\B2BServerCDW\\b2bHandleCDW.exe;PID=0x404;THREAD=0xa40;VERSION=17.0.0.1062;API=ODBC;TIMEZONEADJUSTMENT=60
I. 11/22 00:26:55. Connection ID 24034: "usr" disconnected from database "MYDB"
I. 11/22 00:26:55. Connection ID 24034: Client disconnected
I. 11/22 00:27:04. Cache size adjusted to 4251324K
I. 11/22 00:27:30. Connection ID 25979: connection "reportserver" terminated abnormally; client socket shut down
I. 11/22 00:27:30. Connection ID 25979: Disconnected TCPIP client's AppInfo is IP=192.168.96.25;HOST=BG-NLRP1;OSUSER=BGAS2SA;OS='Windows 2012R2 Build 9200 ';EXE=C:\\apps\\CDWReportServer\\CDWReportServer.exe;PID=0x6c4;THREAD=0xf3c;VERSION=17.0.0.1062;API=ODBC;TIMEZONEADJUSTMENT=60
I. 11/22 00:27:30. Connection ID 25979: "reportserver" disconnected from database "MYDB"
I. 11/22 00:27:30. Connection ID 25979: Client disconnected
I. 11/22 00:28:04. Cache size adjusted to 4251208K
I. 11/22 00:29:04. Cache size adjusted to 4251176K
I. 11/22 00:30:00. Starting checkpoint of "MYDB" (MYDB.db) at Wed Nov 22 2017 00:30

==================================================================

SQL Anywhere Network Server Version 17.0.0.1062

Workgroup Edition


Copyright © 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Use of this software is governed by the SAP Software Use Rights Agreement.
Refer to http://global.sap.com/corporate-en/our-company/agreements/index.epx.


Processors detected: 4 logical processor(s) on 4 core(s) on 4 physical processor(s)
Processor license restriction (Workgroup Edition): all logical processors on all cores on up to 2 physical processors
Processor license restriction (licensed processors): all logical processors on all cores on up to 2 physical processors
This server is licensed to use: all logical processors on all cores on up to 2 physical processors
Processors in use by server: 2 logical processor(s) on 2 core(s) on 2 physical processor(s)
This server is licensed to:
    Administrator
    MyCompany
Running Windows 2012R2 Build 9600  on X86_64
Server built for X86_64 processor architecture
4231168K of memory used for caching
Minimum cache size: 4231168K, maximum cache size: 15095340K
Using a maximum page size of 4096 bytes

Starting database "MYDB" (E:\\MYDB\\MYDB.db) at Thu Nov 02 2017 22:36
Transaction log: F:\\MYDB\\MYDB.log
Database "MYDB" (MYDB.db) started at Thu Nov 02 2017 22:36
Database server started at Thu Nov 02 2017 22:36
HTTP listener starting on port 9091
Now accepting requests

======
startup parameters:
------------------
-x tcpip(PORT=4002)
-xs http(port=9091)
-ti 0
-c 4G

[chris_keating]

This is likely either an issue at the client such as a crash or a network issue that is interpreted as the client having gone away abnormally. You can add communication debugging to help diagnose.

On the client, add LogFile=<filespec> connection parameter. This will log client side information about the connection including more detailed information about any client side errors that may have occurred.

On the server, you can enable DebuggingInformation as follows:

call sa_server_option( 'DebuggingInformation', 'On' );

If you are not currently using an console log file, you can enable such logging as follows (set filespec to file - if the path is not supplied, the file should be created in the same location as the database file)

call sa_server_option( 'ConsoleLogFile', '<filespec>' );

If there are TDS connections, you may want to suppress TDS logging as it can be quite verbose. To do so,

set option public.suppress_tds_debugging = 'Off'

Server logging can be stopped by running the same set of statements and setting 'Yes' to 'No' and vice versa and setting the ConsoleLogFile to an empty string - ''.

I would collect logging that captures a few cases of the abnormal disconnect. The logs should provide guidance.