WCCOAopcuasrv appears not to be able to handle more than 163666 datapoints

[RudiKreiner]

I want to publish a whole bunch of datapoints in an OPC UA server on a WinCC OA V3.14 P008 project.
The server starts OK if I add a list of about 150000 datapoints to the dpGroup "OPCUARead"
I then tried it with 178069 datapoints and then get the following output during the manager start.
The first datapoint mentioned to which the server cannot connect is the 163667th one in my list.

WCCOAopcuasrv(4), 2017.07.21 17:35:04.774, SYS, INFO, 1, Manager Start, PROJ, Standard, V 3.14 - 3.14 platform Linux x86_64 linked at Dec 1 2016 11:58:16
WCCOAopcuasrv(4), 2017.07.21 17:35:04.774, SYS, INFO, 3, Trying to connect to (SYS: 0 Data -num 0 CONN: 1) @ Standard:4101
WCCOAopcuasrv(4), 2017.07.21 17:35:04.775, SYS, INFO, 4, Connected to (SYS: 0 Data -num 0 CONN: 1) @ localhost (::1)
WCCOAopcuasrv(4), 2017.07.21 17:35:07.949, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAopcuasrv(4), 2017.07.21 17:35:07.950, SYS, INFO, 3, Trying to connect to (SYS: 1 Event -num 0 CONN: 1) @ Standard:6101
WCCOAopcuasrv(4), 2017.07.21 17:35:07.950, SYS, INFO, 4, Connected to (SYS: 1 Event -num 0 CONN: 1) @ localhost (::1)
WCCOAopcuasrv(4), 2017.07.21 17:35:07.957, SYS, INFO, 103, User names/passwords initialized
WCCOAopcuasrv(4), 2017.07.21 17:35:07.978, PARAM,INFO, 26/opcuasrv, OpcUaSServerConfig in Function getEndpointConfiguration, Start UP OPCUA @ opc.tcp://Standard:4840
WCCOAopcuasrv(4), 2017.07.21 17:35:07.992, PARAM,INFO, 13/opcuasrv, OpcUaSComm in Function boot, OPCUA Boot procedure successful - Setup address space.
WCCOAopcuasrv(4), 2017.07.21 17:36:18.447, SYS, SEVERE, 39, Connection lost, Send buffer limit exceeded, closing connection to (SYS: 1 Event -num 0 CONN: 1) @ localhost, [PeerItcIOHandler::sendCall]
WCCOAopcuasrv(4), 2017.07.21 17:36:18.595, PARAM,SEVERE, 6/opcuasrv, OpcUaSGroupHotlinkWFA in Function hotLinkCallBack, Invalid DpMessage-Answere arrived
WCCOAopcuasrv(4), 2017.07.21 17:36:18.595, SYS, SEVERE, 39, Connection lost, DP: Standard0101:_DpGroup00016_Public.Dps:_online.._value, MAN: (SYS: 1 Device -num 4 CONN: 1), (SYS: 1 Event -num 0 CONN: 1) Waiting for answer from closed connection
WCCOAopcuasrv(4), 2017.07.21 17:36:18.595, PARAM,SEVERE, 6/opcuasrv, OpcUaSGroupHotlinkWFA in Function hotLinkCallBack, Invalid DpMessage-Answere arrived
WCCOAopcuasrv(4), 2017.07.21 17:36:18.595, SYS, SEVERE, 39, Connection lost, DP: Standard0101:_DpGroup00015_Public.Dps:_online.._value, MAN: (SYS: 1 Device -num 4 CONN: 1), (SYS: 1 Event -num 0 CONN: 1) Waiting for answer from closed connection
WCCOAopcuasrv(4), 2017.07.21 17:36:19.234, SYS, WARNING, 65, Wrong destination address, (SYS: 1 Event -num 0 CONN: 1), DP_MSG_CONNECT
WCCOAopcuasrv(4), 2017.07.21 17:36:19.236, PARAM,SEVERE, 23/opcuasrv, OpcUaSPIValueItem in Function dpConnectNOSOURCE, Can not connect to DPE Standard0101:StrTdoOutGas.Ann001.TmpBur002.Clg.VlvMaxRawCmd
WCCOAopcuasrv(4), 2017.07.21 17:36:19.236, SYS, WARNING, 65, Wrong destination address, (SYS: 1 Event -num 0 CONN: 1), DP_MSG_CONNECT
WCCOAopcuasrv(4), 2017.07.21 17:36:19.237, PARAM,SEVERE, 23/opcuasrv, OpcUaSPIValueItem in Function dpConnectNOSOURCE, Can not connect to DPE Standard0101:StrTdoOutGas.Ann001.TmpBur002.Clg.VlvMaxRawStt
WCCOAopcuasrv(4), 2017.07.21 17:36:19.237, SYS, WARNING, 65, Wrong destination address, (SYS: 1 Event -num 0 CONN: 1), DP_MSG_CONNECT
WCCOAopcuasrv(4), 2017.07.21 17:36:19.238, PARAM,SEVERE, 23/opcuasrv, OpcUaSPIValueItem in Function dpConnectNOSOURCE, Can not connect to DPE Standard0101:StrTdoOutGas.Ann001.TmpBur002.Clg.VlvMinRawCmd
:
I get similar messages for each of the remaining 15000 datapoints, then the output continues as follows:
:
WCCOAopcuasrv(4), 2017.07.21 17:36:27.597, SYS, WARNING, 65, Wrong destination address, (SYS: 1 Event -num 0 CONN: 1), DP_MSG_CONNECT
WCCOAopcuasrv(4), 2017.07.21 17:36:27.597, PARAM,SEVERE, 23/opcuasrv, OpcUaSPIValueItem in Function dpConnectNOSOURCE, Can not connect to DPE Standard0101:StrTdoTdx.WarProInv.Vrs
WCCOAopcuasrv(4), 2017.07.21 17:36:27.597, SYS, WARNING, 65, Wrong destination address, (SYS: 1 Event -num 0 CONN: 1), DP_MSG_CONNECT
WCCOAopcuasrv(4), 2017.07.21 17:36:27.598, PARAM,SEVERE, 23/opcuasrv, OpcUaSPIValueItem in Function dpConnectNOSOURCE, Can not connect to DPE Standard0101:StrTdoTdx.WarProInv.Wsu
WCCOAopcuasrv(4), 2017.07.21 17:36:27.765, SYS, INFO, 4, Connected to (SYS: 1 Event -num 0 CONN: 1) @ localhost (::1)
WCCOAopcuasrv(4), 2017.07.21 17:37:32.848, PARAM,WARNING, 20/opcuasrv, OpcUaSComm in Function write, Can not write value to Node ns=2;s=STR_TDOOUTGAS.StrTdoOutGas.War.Sum (Statuscode: $4)
WCCOAopcuasrv(4), 2017.07.21 17:37:32.849, PARAM,WARNING, 20/opcuasrv, OpcUaSComm in Function write, Can not write value to Node ns=2;s=STR_TDOOUTGAS.StrTdoOutGas.War.Sum (Statuscode: $4)
WCCOAopcuasrv(4), 2017.07.21 17:37:32.849, PARAM,WARNING, 20/opcuasrv, OpcUaSComm in Function write, Can not write value to Node ns=2;s=STR_TDOOUTGAS.StrTdoOutGas.TmpAllStaMod.SetStt (Statuscode: $4)
WCCOAopcuasrv(4), 2017.07.21 17:37:32.849, PARAM,WARNING, 20/opcuasrv, OpcUaSComm in Function write, Can not write value to Node ns=2;s=STR_TDOOUTGAS.StrTdoOutGas.TmpAllStaMod.SetStt (Statuscode: $4)
WCCOAopcuasrv(4), 2017.07.21 17:37:32.849, PARAM,WARNING, 20/opcuasrv, OpcUaSComm in Function write, Can not write value to Node ns=2;s=STR_TDOOUTGAS.StrTdoOutGas.TmpAllStaMod.SetCmd (Statuscode: $4)
WCCOAopcuasrv(4), 2017.07.21 17:37:32.849, PARAM,WARNING, 20/opcuasrv, OpcUaSComm in Function write, Can not write value to Node ns=2;s=STR_TDOOUTGAS.StrTdoOutGas.TmpAllStaMod.SetCmd (Statuscode: $4)
WCCOAopcuasrv(4), 2017.07.21 17:37:32.849, PARAM,WARNING, 20/opcuasrv, OpcUaSComm in Function write, Can not write value to Node ns=2;s=STR_TDOOUTGAS.StrTdoOutGas.TmpAll.ZonEnaCou (Statuscode: $4)
WCCOAopcuasrv(4), 2017.07.21 17:37:32.849, PARAM,WARNING, 20/opcuasrv, OpcUaSComm in Function write, Can not write value to Node ns=2;s=STR_TDOOUTGAS.StrTdoOutGas.TmpAll.ZonEnaCou (Statuscode: $4)
WCCOAopcuasrv(4), 2017.07.21 17:37:32.850, PARAM,WARNING, 20/opcuasrv, OpcUaSComm in Function write, Can not write value to Node ns=2;s=STR_TDOOUTGAS.StrTdoOutGas.TmpAll.ZonCou (Statuscode: $4)
WCCOAopcuasrv(4), 2017.07.21 17:37:32.850, PARAM,WARNING, 20/opcuasrv, OpcUaSComm in Function write, Can not write value to Node ns=2;s=STR_TDOOUTGAS.StrTdoOutGas.TmpAll.ZonCou (Statuscode: $4)

I'm testing the interface using the UaExpert client and have no problem making a connection with the 150000 datapoint connection.

With 178069 datapoints, I get the following feedback from UaExpert:

(note that the entries are in reverse chronological order, ie bottom to top)
17:54:22.269 | Server Node | WinCC_OA@Standard Standard/... | Connecting failed with error 'BadOutOfMemory'
17:54:22.258 | Server Node | WinCC_OA@Standard Standard/... | Error 'BadOutOfMemory' was returned during CreateSession
17:54:22.179 | Server Node | WinCC_OA@Standard Standard/... | Used UserTokenType: Anonymous
17:54:22.179 | Server Node | WinCC_OA@Standard Standard/... | ApplicationUri: 'urn:Standard:WinCC_OA:Standard:4'
17:54:22.179 | Server Node | WinCC_OA@Standard Standard/... | Security policy: 'http://opcfoundation.org/UA/SecurityPolicy#None'
17:54:22.179 | Server Node | WinCC_OA@Standard Standard/... | Endpoint: 'opc.tcp://Standard:4840'
17:54:21.719 | UaExpert | | UaExpert is ready to use.

Am I doing something wrong here or is this some intrinsic limitation in WinCC OA?

Is there anything I can do to increase the number of datapoints the server can handle
(other than splitting up my datapoints among multiple servers which I really don't want to do if I don't have to)?

[kilianvp]

maybe you hit the dpConnect limit?

[Gertjan van Schijndel]

Rudi Kreiner wrote:

WCCOAopcuasrv(4), 2017.07.21 17:36:18.447, SYS, SEVERE, 39, Connection lost, Send buffer limit exceeded, closing connection to (SYS: 1 Event -num 0 CONN: 1) @ localhost, [PeerItcIOHandler::sendCall]

It looks like the send buffer limit has exceeded the limit. You could try to increase the limit timeout with the config entry 'bcmBufferLimitTimeout' and/or increase the buffer size with 'maxBcmBufferSize'.

[RudiKreiner]

Taking a closer look at that log entry, that certainly makes sense. I'll give that a try. Thanks for your help.