NMS IccpAdapter Prints Voluminous Extra Debug Lines In Its Logfiles
(Doc ID 2505322.1)
Last updated on JULY 22, 2021
Applies to:
Oracle Utilities Network Management System - Version 1.11.0.4 and laterOracle Network Management for Utilities - DMS - Version 1.11.0.4 and later
Information in this document applies to any platform.
Symptoms
NMS IccpAdapter prints voluminous extra debug lines in its logfiles
We use the IccpAdapter to communicate with the SCADA system through an Iccp protocol interface. The IccpAdapter unexpectedly prints extra debug lines.
01/11 16:29:55: IccpAdapter 0x8,ctp=0x00000001007ab1d8,"writeLoop" IccpSocket::freeMem - glMemCount=-1
01/11 16:29:55: IccpAdapter 0x4,ctp=0x00000001002155a8,"debugstream.C/debug_thread" IccpSocket::freeMem - glMemCount=-1
01/11 16:29:58: IccpAdapter 0x8,ctp=0x00000001007ab1d8,"writeLoop" IccpSocket::freeMem - glMemCount=-1
01/11 16:29:58: IccpAdapter 0x4,ctp=0x00000001002155a8,"debugstream.C/debug_thread" IccpSocket::freeMem - glMemCount=-1
It is expected that the adapter should log less that it does by default. Due to this amount of logging, there is a concern that the log file will grow to the point where the system runs out of allocated disk space.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |