SoapServerApp
Alarms
The following 192 alarms may be generated by N2SVCD Application “SoapServerApp”.
No alarms found that match search criteria.
SV-AP-10000 WARNING | Connection | Error sending statistics: %s |
Cause: An error was encountered sending application statistics. |
%s = The error that occurred when sending statistics. |
Resolution: Review N2SVCD statistics configuration. Ensure the endpoint is available. |
SV-AP-10002 WARNING | Configuration | Unknown Peer Application [%s]. |
Cause: Received request to get handle for unknown peer application. |
%s = The peer application name. |
Resolution: Review requested peer application name. Review application configuration. |
SV-AP-10003 WARNING | Connection | Failed to discover application name [%s] for [%s]: %s |
Cause: Failed discovery of an application name. |
%s = The application name which cannot be discovered/resolved. %s = The label specified at the time of requesting. %s = Additional reason description for the failure. |
Resolution: Check that the remote application container is started, correctly configured, and is reachable, and that the container services API is correctly configured and available. |
SV-AP-10004 NOTICE | Connection | Successful discovery of application name [%s] for [%s]. |
Cause: Successful discovery of an application name. |
%s = The application name which was successfully discovered/resolved. %s = The label specified at the time of requesting. |
Resolution: None. |
SV-AP-10005 NOTICE | Application | IPC SHM index is %d. |
Cause: Parameter configuration at startup. Configured application SHM information. |
%d = The configured application SHM index. |
Resolution: None. |
SV-AP-10006 NOTICE | Application | Discovery %s (%s) - server [%s:%s]. |
Cause: Parameter configuration at startup. Configured application discovery information. |
%s = Are we the discovery server or the client? %s = The configured socket discovery type. %s = The configured socket discovery host. %s = The configured socket discovery port. |
Resolution: None. |
SV-AP-10007 NOTICE | Application | IPC Socket Listen Port = %d. |
Cause: Parameter configuration at startup. Configured IPC socket listen port. |
%d = The IPC port on which this application accepts IPC message connections. |
Resolution: None. |
SV-AP-10008 WARNING | Connection | Failed to create client socket for app '%s:%s' endpoint %s:%d: %s. |
Cause: Failed to create a new socket client handle. |
%s = The application name. %s = The application subname (supplied or auto-generated). %s = The remote IP. %d = The remote TCP port. %s = The error description. |
Resolution: Check that endpoint address is reachable. |
SV-AP-10009 WARNING | Configuration | EDR App Name '%s' discovery failed: %s |
Cause: EDR application discovery immediate failure. |
%s = The EDR application name. %s = The reason for immediate failure. |
Resolution: Check EDR agent application name configuration. |
SV-AP-10012 NOTICE | Application | Trace Level is '%s'. |
Cause: Parameter configuration at startup. Configured application trace level. |
%s = The configured application trace level. |
Resolution: None. |
SV-AP-10013 NOTICE | Application | Trace Level Max is '%s'. |
Cause: Parameter configuration at startup. Configured application max trace level. |
%s = The configured max trace level. |
Resolution: None. |
SV-AP-10014 NOTICE | Application | Trace Per Second is '%s'. |
Cause: Parameter configuration at startup. Configured application trace per second. |
%s = The configured trace per second. |
Resolution: None. |
SV-AP-10015 NOTICE | Application | Retaining '%d' shutdown instances. |
Cause: Parameter configuration at startup. Configured application instance retention count. |
%d = The configured shutdown instance retention count. |
Resolution: None. |
SV-AP-10016 NOTICE | Application | Statistics Slice Count is '%s'. |
Cause: Parameter configuration at startup. Configured application statistics slice count. |
%s = The configured statistics slice count. |
Resolution: None. |
SV-AP-10017 NOTICE | Application | Statistics Slice Seconds is '%s'. |
Cause: Parameter configuration at startup. Configured application statistics slice seconds. |
%s = The configured statistics slice seconds. |
Resolution: None. |
SV-AP-10019 NOTICE | Application | EDR Application Name = '%s'. |
Cause: Parameter configuration at startup. Configured EDR application name. |
%s = The configured EDR application name. |
Resolution: None. |
SV-AP-10020 NOTICE | Application | EDR Default Stream = '%s'. |
Cause: Parameter configuration at startup. Configured EDR stream. |
%s = The configured EDR stream. |
Resolution: None. |
SV-AP-10021 WARNING | Configuration | Cannot write EDRs. Configured EDR App '%s' was not available at showtime. |
Cause: Configured EDR application to utilize does not map to known application. |
%s = The name of the EDR app that is not known. |
Resolution: Check application configuration defines configured EDR application. Check configured EDR application exists and is configured. |
SV-AP-10023 WARNING | Job | Unable to update parameter '%s' to value '%s': %s |
Cause: SNMP set request could not be completed due to update failure. |
%s = The parameter to update. %s = The received new value for the parameter. %s = The error that prevents the new value being used. |
Resolution: Review error message and validate received message parameters accordingly. |
SV-AP-10024 WARNING | Job | Unable to roll back parameter '%s' to value '%s' after update to value '%s': %s |
Cause: SNMP set request could not roll back updated parameter after subsequent update failure. |
%s = The parameter to update. %s = The received new value for the parameter. %s = The original value for the parameter. %s = The error that prevents the value from being rolled back to. |
Resolution: Review error message and validate received message parameters accordingly. |
SV-AP-10029 NOTICE | Application | EDRs are Supported but NOT Enabled. |
Cause: Parameter configuration at startup. Application supports EDRs but they are not enabled. | - |
Resolution: None. |
SV-AP-10030 WARNING | Application | Application did not handle timeout reason '%s'. |
Cause: Received timeout that the underlying application did not handle. |
%s = The reason the timeout was not handled. |
Resolution: Contact N-Squared support. |
SV-AP-10031 NOTICE | Application | Configuration Scalar Update of '%s' %s. |
Cause: Application configuration scalar value updated. |
%s = The configuration key that was updated. %s = Whether or not the update was successful. |
Resolution: None. |
SV-AP-10032 NOTICE | Application | Configuration Vector Change of '%s' [%s] Succeeded. |
Cause: Application configuration vector updated. |
%s = The updated configuration key. %s = The update action. |
Resolution: None. |
SV-AP-10033 ALARM | Application | Application self transition from %s -> %s. |
Cause: Application access has transitioned between ONLINE <=> SHUTDOWN/OFFLINE/QUIESCE. |
%s = The original access level name (ONLINE). %s = The new access level name (SHUTDOWN/OFFLINE/QUIESCE). |
Resolution: Confirm that this state change is expected. |
SV-AP-10033 CLEAR | Application | Application self transition from %s -> %s. |
Cause: Application access has transitioned between SHUTDOWN/OFFLINE/QUIESCE <=> ONLINE. |
%s = The original access level name (SHUTDOWN/OFFLINE/QUIESCE). %s = The new access level name (ONLINE). |
Resolution: None. |
SV-AP-10034 WARNING | Internal | Instance [%s] already over when performing instance_over(). |
Cause: Instance received duplicate 'over' handler. |
%s = Instance index. |
Resolution: Contact N-Squared support. |
SV-AP-10035 WARNING | Internal | Instance [%s] not found when performing instance_over(). |
Cause: Instance not found when performing 'over' handler. |
%s = Instance index. |
Resolution: Contact N-Squared support. |
SV-AP-10038 WARNING | Internal | Failed to cancel timer [%s]: %s |
Cause: Failed to cancel in progress timer. |
%s = The reason the timer could not be canceled. %s = The error result when trying to cancel the timer. |
Resolution: Review the associated error reason. Review the associated error result. Contact N-Squared support. |
SV-AP-10039 WARNING | Internal | Discarding Message from unknown sender '%s'. |
Cause: Received application message from unknown sender. |
%s = The unknown sender. |
Resolution: Contact N-Squared support. |
SV-AP-10040 WARNING | Internal | Failed to process administrative message %s from %s: %s |
Cause: Failed to process admin queue message. |
%s = The message. %s = The sending application identifier (handle key). %s = The error result when trying to read from the message queue. |
Resolution: Contact N-Squared support. |
SV-AP-10041 WARNING | Internal | Failed to process user message %s from %s: %s |
Cause: Failed to process user queue message. |
%s = The message. %s = The sending application identifier (handle key). %s = The error result when trying to read from the message queue. |
Resolution: Contact N-Squared support. |
SV-AP-10042 WARNING | Configuration | Configuration Request for '%s' (%s) Failed: %s |
Cause: Failed to query application configuration vector. |
%s = The configuration key. %s = The configuration row key. %s = The error result when trying to query the configuration vector. |
Resolution: Review the associated error result. Check the inbound message content construction. |
SV-AP-10043 WARNING | Message | Resources Request for '%s' (%s) Failed: %s |
Cause: Failed to query application resource. |
%s = The resource key. %s = The resource key row. %s = The error result when trying to query the resource. |
Resolution: Review the associated error result. Check the inbound message content construction. |
SV-AP-10044 WARNING | Configuration | Configuration Update of '%s' Failed: %s |
Cause: Failed to update application configuration scalar. |
%s = The configuration key. %s = The error result when trying to update the configuration scalar. |
Resolution: Review the associated error result. Check the configuration update message content construction. |
SV-AP-10045 WARNING | Internal | Received instance message %s with no context. Discarding. |
Cause: Received instance message with no context. |
%s = The message. |
Resolution: Review message construction. Ensure instance message contains instance context. |
SV-AP-10046 WARNING | Configuration | Configuration environment translation for '\${%s}' is not defined. |
Cause: Configuration environment not defined. |
%s = The configuration variable name. |
Resolution: Check environment configuration. |
SV-AP-10047 WARNING | Configuration | Command `%s` failed to execute: %s |
Cause: Failed to execute variable command. |
%s = The error message generated when trying to execute the command. %s = The command. |
Resolution: Review the associated command error. Check application execution permissions. Check command syntax and structure. |
SV-AP-10048 WARNING | Configuration | Command `%s` died with signal %d. |
Cause: Variable command execution exited with non-zero exit code. |
%s = The command. %d = The exit signal. |
Resolution: Review the associated error signal. Check application execution permissions. Check command syntax and structure. |
SV-AP-10049 WARNING | Configuration | Command `%s` exited with non-zero value %d. |
Cause: Variable command execution exited with non-zero exit code. |
%s = The command. %d = The exit code. |
Resolution: Review the associated exit code. Check command syntax and structure. |
SV-AP-10050 WARNING | Resource Configuration | Hostname '%s' is not known. |
Cause: Failed to convert Hostname into address. Hostname is not known. |
%s = The hostname. |
Resolution: Check Hostname configuration. Check address configuration. Check DNS availability. |
SV-AP-10051 WARNING | Internal | Unhandled Message '%s' for Context '%s' from App '%s'. |
Cause: Application unable to handle message. |
%s = The message. %s = The message context. %s = The sending application identifier (handle key). |
Resolution: Contact N-Squared support. |
SV-AP-10052 ALARM | Application | Application is now OVERLOADED. |
Cause: Application is now overloaded to the point where processing is affected. | - |
Resolution: Check application traffic levels and configuration. |
SV-AP-10052 CLEAR | Application | Application is now %s (not OVERLOADED). |
Cause: Application is no longer overloaded. |
%s = The new loading level (NORMAL or HIGH) |
Resolution: None. |
SV-AP-10053 NOTICE | Application | Throttle Enabled: max %d instances, max tps (%d average over %d secs). |
Cause: Parameter configuration at startup. Configured application throttling parameters. |
%d = The configured maximum active instance count. %d = The configured maximum TPS (new instances per second). %d = The configured sliding window (in seconds) for measuring TPS. |
Resolution: None. |
SV-AP-10054 ALARM | Application | Application is now at HIGH LOAD. |
Cause: Application is now at high-load (processing is not yet affected). | - |
Resolution: Check application traffic levels and configuration. |
SV-AP-10054 CLEAR | Application | Application is now %s (not HIGH LOAD). |
Cause: Application is no longer at high-load. |
%s = The new loading level (NORMAL) |
Resolution: None. |
SV-AP-10056 NOTICE | Application | Resource Vector Operation '%s' Succeeded. |
Cause: Application resource vector operation successful. |
%s = The vector operation key. |
Resolution: None. |
SV-AP-10057 WARNING | Internal | Error thawing %d byte envelope: %s |
Cause: Failed to thaw message byte envelope. |
%d = The message envelope length. %s = The error that occurred trying to thaw the payload. |
Resolution: Contact N-Squared support. |
SV-AP-10058 WARNING | Configuration | Resource Operation of '%s' Failed: %s |
Cause: Failed to perform resource operation. |
%s = The resource key. %s = The error result when trying to perform the resource operation. |
Resolution: Review the associated error result. Check the configuration update message content construction. |
SV-AP-10201 WARNING | Job | Shutdown/Abort: %s |
Cause: A single instance has received an unexpected shutdown/abort message. Depending on the application, an "instance" may represent a transaction, call, session, request/response pair, etc. |
%s = The abort reason. |
Resolution: Review the associated abort reason for further details. |
SV-AP-10202 WARNING | Configuration | Cannot write EDRs. EDR Application Name is not correctly configured. |
Cause: Cannot write EDR due to no configured EDR application. | - |
Resolution: Check configured EDR application exists and is configured. |
SV-AP-10203 WARNING | Store | Discarded EDR event '%s' after shutdown. |
Cause: Received EDR write event after application shutdown. |
%s = EDR event. |
Resolution: Review the associated triggering event. Review shutdown procedure. Ensure no traffic is being processed when application shutdown is triggered. |
SV-AP-10204 WARNING | Store | Failed sending EDR to EdrApp: %s |
Cause: Failed to send EDR record to EDR writer process. |
%s = The error result when attempting to write the EDR to the writer process. |
Resolution: Review the associated error result. Contact N-Squared support. |
SV-AP-10205 WARNING | Internal | Unhandled timer '%s' (discarded). |
Cause: Received timeout that the underlying application did not handle timeout. The timer was discarded. |
%s = The reason the timeout was not handled. |
Resolution: Contact N-Squared support. |
SV-AP-10206 WARNING | Internal | Unhandled message '%s' (discarded). |
Cause: A message was received that was not handled. The message was discarded. |
%s = The unhandled message. |
Resolution: Contact N-Squared support. |
SV-AP-10301 WARNING | Internal | send_message 'sender_context' must be SCALAR. |
Cause: Attempting to send message to application handle that contains non SCALAR 'sender_context'. | - |
Resolution: Contact N-Squared support. |
SV-AP-10302 WARNING | Internal | send_message 'context' must be SCALAR. |
Cause: Attempting to send message to application with non SCALAR context. | - |
Resolution: Contact N-Squared support. |
SV-AP-10303 WARNING | Internal | send_message 'details' must be undef/HASH. |
Cause: Attempting to send message to application with non SCALAR/HASH/ARRAY details. | - |
Resolution: Contact N-Squared support. |
SV-AP-10304 WARNING | Internal | Queue of non-management '%s' from '%s' to '%s' failed. Application status = STATUS_SHUTDOWN. |
Cause: Received non-administrative message while in application shutdown. |
%s = Message. %s = Sender name. %s = Application name. |
Resolution: Contact N-Squared support. |
SV-AP-10305 WARNING | Internal | ERROR cloning %s message parameters: %s |
Cause: Failed to clone message parts for delivery in single-process. |
%s = The message type being cloned at this time. %s = The error that occurred trying to clone the message part. |
Resolution: Contact N-Squared support. |
SV-AP-10306 WARNING | Internal | Queue '%s' to App '%s' (%s -> %s) failed: %s |
Cause: Failed to queue message to application. |
%s = Message. %s = Application name. %s = Sender context. %s = Context. %s = The error result message. |
Resolution: Contact N-Squared support. |
SV-AP-10401 WARNING | Internal | send_message 'sender_context' must be SCALAR. |
Cause: Attempting to send shm IPC message to application handle that contains non SCALAR 'sender_context'. | - |
Resolution: Contact N-Squared support. |
SV-AP-10402 WARNING | Internal | send_message 'context' must be SCALAR. |
Cause: Attempting to send shm IPC message to application with non SCALAR context. | - |
Resolution: Contact N-Squared support. |
SV-AP-10403 WARNING | Internal | send_message 'details' must be undef/HASH. |
Cause: Attempting to send shm IPC message to application with non SCALAR/HASH/ARRAY details. | - |
Resolution: Contact N-Squared support. |
SV-AP-10409 WARNING | Internal | ERROR freezing (N2 encoding) %s message: %s |
Cause: Failed to freeze message (N2 encoding) for delivery in socket IPC. |
%s = The message type being frozen at this time. %s = The error that occurred trying to freeze the message. |
Resolution: Contact N-Squared support. |
SV-AP-10410 WARNING | Message | Failed to write SHM message %s to %s (%s Queue): %s |
Cause: Failed to write message to SHM queue. Most likely full. |
%s = Message name. %s = Target application name. %s = Is administrative message. %s = Reason for write failure. |
Resolution: Check if target applications are overloaded and responding. Check the if the target applications are processing load. Check if downstream applications are accepting and processing requests. |
SV-AP-10701 WARNING | Internal | send_message 'sender_context' must be SCALAR. |
Cause: Attempting to send socket IPC message to application handle that contains non SCALAR 'sender_context'. | - |
Resolution: Contact N-Squared support. |
SV-AP-10702 WARNING | Internal | send_message 'context' must be SCALAR. |
Cause: Attempting to send socket IPC message to application with non SCALAR context. | - |
Resolution: Contact N-Squared support. |
SV-AP-10703 WARNING | Internal | send_message 'details' must be undef/HASH. |
Cause: Attempting to send socket IPC message to application with non SCALAR/HASH/ARRAY details. | - |
Resolution: Contact N-Squared support. |
SV-AP-10709 WARNING | Internal | ERROR freezing (BSON encoding) %s message: %s |
Cause: Failed to freeze message (BSON encoding) for delivery in socket IPC. |
%s = The message type being frozen at this time. %s = The error that occurred trying to freeze the message. |
Resolution: Contact N-Squared support. |
SV-AP-10710 WARNING | Message | Failed to write socket message %s to %s (%s Queue): %s |
Cause: Failed to write message to socket queue. |
%s = Message name. %s = Target application name. %s = Is administrative message (does not affect writing). %s = Reason for write failure. |
Resolution: Check if target applications are overloaded and responding. Check the if the target applications are processing load. Check if downstream applications are accepting and processing requests. |
SV-AP-10501 NOTICE | Application | Outbound IPC (%s|%s) (%s -> %s) [%s]. |
Cause: Application outbound (client) socket connection has identified the peer endpoint. |
%s = Our application real name. %s = The discovery name by which we found the peer. %s = The local bind IPs/port %s = The remote peer IPs/port %s = The peer self-identified endpoint name |
Resolution: None. |
SV-AP-10502 WARNING | Connection | Lost IPC connection to peer (%s) [%s]: %s |
Cause: Application outbound (client) socket connection has been lost. |
%s = The local handle key by which we identify the peer %s = The peer self-identified endpoint name %s = The error message associated with the connection failure. |
Resolution: Review the associated error message. Check configuration and network status. |
SV-AP-10503 NOTICE | Application | Ended IPC connection to peer (%s) [%s]: %s |
Cause: Application outbound (client) socket connection has been ended during shutdown. |
%s = The local handle key by which we identify the peer %s = The peer self-identified endpoint name %s = The error message associated with the connection failure. |
Resolution: None. |
SV-AP-10504 WARNING | Internal | ERROR thawing %d byte BSON envelope: %s |
Cause: Failed to thaw message BSON byte envelope. |
%d = The message envelope length. %s = The error that occurred trying to thaw the payload. |
Resolution: Contact N-Squared support. |
SV-AP-10601 NOTICE | Application | Inbound IPC (%s) (%s -> %s) [%s]. |
Cause: Application inbound (server) socket connection has identified the peer endpoint. |
%s = The local handle key containing the real peer name and the discovery name by which we were reached. %s = The remote peer host IPs/port %s = The local host IPs/port %s = Our own real application name. |
Resolution: None. |
SV-AP-10602 WARNING | Internal | ERROR thawing %d byte BSON envelope: %s |
Cause: Failed to thaw message BSON byte envelope. |
%d = The message envelope length. %s = The error that occurred trying to thaw the payload. |
Resolution: Contact N-Squared support. |
SV-AP-10603 NOTICE | Application | Lost IPC connection [%s]: %s |
Cause: Application inbound (server) socket connection has been lost. |
%s = The handle key containing the peer name and our public name %s = The error message associated with the connection failure. |
Resolution: Review the associated error message. Check configuration and network status. |
SV-TP-10000 WARNING | Configuration | Parameter 'num_client_connections' will override DEPRECATED parameter 'pool'. |
Cause: Parameter configuration at startup. Both Overriding | - |
Resolution: Check configuration for use of |
SV-TP-10001 WARNING | Configuration | Parameter 'pool' is DEPRECATED. Please use 'num_client_connections' instead. |
Cause: Parameter configuration at startup. Using obsolete pool configuration. | - |
Resolution: Check configuration for use of |
SV-TP-10002 WARNING | Configuration | Ping Interval configured but application does not support ping. |
Cause: Parameter configuration at startup.
| - |
Resolution: Check configuration and remove |
SV-TP-10003 WARNING | Configuration | Ping Always configured but application does not support ping. |
Cause: Parameter configuration at startup.
| - |
Resolution: Check configuration and remove |
SV-TP-10004 WARNING | Connection | Teardown persistent connection after PING failed: %s |
Cause: Persistent connection failed to respond to ping request. |
%s = The error that occurred when performing the ping operation. |
Resolution: Review the associated error result. Check remote the connection is accessible. Check the connection configuration. Check the remote application is up and accepting pings. |
SV-TP-10005 WARNING | Connection | Transient connections PING failed: %s |
Cause: Transient connection failed to respond to ping request. |
%s = The error that occurred when performing the ping operation. |
Resolution: Review the associated error result. Check remote the connection is accessible. Check the connection configuration. Check the remote application is up and accepting pings. |
SV-TP-10006 WARNING | Message | Discarding new user request sent %.1f seconds ago. |
Cause: Application overloaded. User request has been dropped. |
%.1f = The time since the user request was placed on the outbound message queue. |
Resolution: Check if the application is overloaded. Monitor the application for additional dropped requests. |
SV-TP-10010 ALARM | Application | Queue size (%s) now above %s. |
Cause: The message queue has increased past the warning threshold. |
%s = The current size of the message queue. %s = The warning threshold. |
Resolution: Check if application is overloaded and falling behind. Check if application is processing messages successfully. Monitor application load. |
SV-TP-10010 CLEAR | Connection | Queue size (%s) now below %s. |
Cause: The message queue has decreased past the warning threshold. |
%s = The current size of the message queue. %s = The warning threshold. |
Resolution: None. |
SV-TP-10011 WARNING | Message | Error on %s creation: %s |
Cause: Failed to create outbound user request instance. |
%s = The outbound instance class. %s = The error message generated when creating the outbound instance class. |
Resolution: Review the associated error result. Ensure the outbound instance class is a valid outbound instance class. |
SV-TP-10012 NOTICE | Application | Using stream socket in [%s] mode with proto [%s]. |
Cause: Parameter configuration at startup. The socket mode to utilize. |
%s = The configured stream socket mode (client/connect or server/listen). %s = The configured stream socket protocol (TCP or SCTP). |
Resolution: None. |
SV-TP-10013 NOTICE | Application | Using UDP socket. |
Cause: Parameter configuration at startup. Application uses UDP. | - |
Resolution: None. |
SV-TP-10016 NOTICE | Application | Ping Interval = %d. |
Cause: Parameter configuration at startup. The ping interval. |
%d = The configured ping interval. |
Resolution: None. |
SV-TP-10017 NOTICE | Application | Ping Always (even when active) = %d. |
Cause: Parameter configuration at startup. Whether or not |
%d = The configured Ping Always value. |
Resolution: None. |
SV-TP-10018 NOTICE | Application | Reconnect Interval = %d. |
Cause: Parameter configuration at startup. The reconnect interval. |
%d = The configured reconnect interval, must be non-zero INTEGER. |
Resolution: None. |
SV-TP-10019 NOTICE | Application | Backlog Timeout = %d. |
Cause: Parameter configuration at startup. The backlog timeout. |
%d = The configured backlog timeout. |
Resolution: None. |
SV-TP-10020 NOTICE | Application | Server Timeout = %d. |
Cause: Parameter configuration at startup. The server timeout. |
%d = The configured server timeout. |
Resolution: None. |
SV-TP-10021 NOTICE | Application | Max # Send Attempt = %d. |
Cause: Parameter configuration at startup. The max number of send attempts per message. |
%d = The configured max number of send attempts. |
Resolution: None. |
SV-TP-10022 NOTICE | Application | Connection Backlog = %d. |
Cause: Parameter configuration at startup. The maximum number of items int he connection backlog. |
%d = The configured connection backlog. |
Resolution: None. |
SV-TP-10023 NOTICE | Application | Connection Backlog always 1 Maximum (synchronous). |
Cause: Parameter configuration at startup. Outbound connection type is synchronous. Connection backlog defaulting to | - |
Resolution: None. |
SV-TP-10024 NOTICE | Application | Server Timeout = %d. |
Cause: Parameter configuration at startup. The server timeout. |
%d = The configured server timeout. |
Resolution: None. |
SV-TP-10025 NOTICE | Application | Warning Queue (Above) threshold = %d. |
Cause: Parameter configuration at startup. The queue threshold before generating an alarm. |
%d = The configured threshold. |
Resolution: None. |
SV-TP-10026 NOTICE | Application | Notice Queue (Below) threshold = %d. |
Cause: Parameter configuration at startup. The queue threshold before generating a notice. |
%d = The configured threshold. |
Resolution: None. |
SV-TP-10027 NOTICE | Application | Report Queue Warning Period is %d (secs). |
Cause: Parameter configuration at startup. The minimum amount of time between queue threshold alarms before generating another one. |
%d = The configured queue warning period. |
Resolution: None. |
SV-TP-10028 NOTICE | Application | Application will Dynamically define client configuration (e.g. reading from DB). |
Cause: Parameter configuration at startup. Client application enabled with support for both client and server connections. | - |
Resolution: None. |
SV-TP-10029 NOTICE | Application | Configuring as a %s CLIENT (SSL = %s). |
Cause: Parameter configuration at startup. Client application enabled with only support for client connections. |
%s = Client connection proto TCP/SCTP. %s = Do we use SSL for outbound client connections YES/NO. |
Resolution: None. |
SV-TP-10030 NOTICE | Application | Configuring as a %s SERVER (SSL = %s). |
Cause: Parameter configuration at startup. Server application enabled with only support for server operations. |
%s = Server proto TCP/SCTP. %s = Do we use SSL for inbound server connections YES/NO. |
Resolution: None. |
SV-TP-10031 NOTICE | Application | Connecting %d (%s) client connections to [%s:%s]. |
Cause: Application startup is initiating a number of default connections. |
%d = The number of client connections. %s = The type of connection (persistent or transient). %s = The remote host. %s = The remote port. |
Resolution: None. |
SV-TP-10032 NOTICE | Connection | Constructing %s client %s connection to [%s:%s]. |
Cause: Application startup has defined an new explicit client connection. |
%s = The type of connection (persistent or transient). %s = The connection protocol TCP/SCTP. %s = The remote host. %s = The remote port. |
Resolution: None. |
SV-TP-10033 NOTICE | Application | Connecting to listen as %s server on [%s:%s] . |
Cause: Application startup. Preparing to listen as server. |
%s = Server proto UDP/TCP/SCTP. %s = The hosts on which this server listens. %s = The port on which this server listens. |
Resolution: None. |
SV-TP-10034 NOTICE | Application | Using token model [%s] via token app [%s] (retry %d secs). |
Cause: Parameter configuration at startup. The token model and associated attributes. |
%s = The configured token model. %s = The configured token application name. %d = The configured token retry-on-failure interval. |
Resolution: None. |
SV-TP-10035 NOTICE | Application | Connection behavior CASCADE = %s, BALANCE = %s, ROTATE = %s. |
Cause: Parameter configuration at startup. The parameters configured for connection usage. |
%s = Do we cascade/fallback to lower priority when higher priority is backlogged (YES) or only only complete failure (NO). %s = Do we balance connections actively to ensure the lowest backlog across all connections of equal priority. %s = Do we rotate/round-robin connections equally (YES) or do we favor the first-connection (NO). |
Resolution: None. |
SV-TP-10036 NOTICE | Application | Rebinding Server listen hosts %s -> %s. |
Cause: Server configuration updated. Rebind server to new listening host. |
%s = The current listening host. %s = The current listening port. |
Resolution: None. |
SV-TP-10038 WARNING | Configuration | Cannot get token. Configured Token App '%s' is not a currently-available application. |
Cause: Configured token application to utilize does not map to known application. |
%s = The name of the token app that is not known. |
Resolution: Check application configuration defines configured token application. Check configured token application exists and is configured. |
SV-TP-10039 WARNING | Message | Cannot send token request: %s |
Cause: Failed to send request to Token application. |
%s = The error when attempting to send REST-C-REQUEST to the token application. |
Resolution: Check status of the named token application. |
SV-TP-10040 WARNING | Message | Overdue token response from token application. |
Cause: Failed to receive response in time from Token application. This application cannot function without a token. | - |
Resolution: Check status of the named token application. |
SV-TP-10041 NOTICE | Application | Using token path '%s' with ClientId [%s]. |
Cause: Parameter configuration at startup. Amazon Cognito URL path and Client ID. |
%s = The configured token path. %s = The configured token Client ID. |
Resolution: None. |
SV-TP-10042 WARNING | Connection | Token was declined: %s |
Cause: Token request was declined. Application will go OFFLINE. |
%s = The reason for the token grant failure. |
Resolution: Check the associated error message. Contact N-Squared support. |
SV-TP-10083 NOTICE | Application | Rebinding Server listen port %s -> %s. |
Cause: Server configuration updated. Rebind server to new listening port. |
%s = The current listening port. %s = The new listening port. |
Resolution: None. |
SV-TP-10200 WARNING | Message | Error parsing request/response content: %s |
Cause: Failed to parse request/response content. |
%s = The error result that occurred when trying to parse the request/response content. |
Resolution: Review the associated error result. Check message content construction. |
SV-TP-10201 WARNING | Message | Parsed Response did not contain correlation key. Impossible! |
Cause: Response did not contain correlation key. | - |
Resolution: Check message content construction. |
SV-TP-10202 WARNING | Message | Received response for key [%s] which does not match any pending Request. |
Cause: Received response that does not match a pending request. |
%s = The matched index key. |
Resolution: Review associated message key. Check message order. Check message content construction. |
SV-TP-10203 WARNING | Message | Response received, but we did not send a Request for synchronous connection. |
Cause: Response received but no request sent on synchronous connection. | - |
Resolution: Check message order. Review inbound message content. |
SV-TP-10204 NOTICE | Connection | Login completed OK to %s. |
Cause: Login successfully completed for non-persistent connection. |
%s = The remote IPs/port. |
Resolution: None. |
SV-TP-10205 WARNING | Message | Login response is not ACK: %s |
Cause: Received login response that is not an ACK. |
%s = The result message generated from the login response. |
Resolution: Check login response message content construction. |
SV-TP-10206 ALARM | Connection | Terminating connection after login failure: %s |
Cause: Terminating persistent connection after failed login. |
%s = The result message generated from the failed login. |
Resolution: Review the associated error result. Check login configuration. Check if remote application is available and accepting login requests. |
SV-TP-10206 CLEAR | Connection | Login completed OK to %s. |
Cause: Login successfully completed for persistent connection. |
%s = The remote IPs/port. |
Resolution: None. |
SV-TP-10207 WARNING | Configuration | Parsed request did not contain correlation key. |
Cause: Parsed request did not contain correlation key. | - |
Resolution: Check request message content construction. |
SV-TP-10208 NOTICE | Message | Discarding request for duplicate key [%s] which is already being handled. |
Cause: Received duplicate inbound request that is already being processed. Inbound request discarded. |
%s = The duplicate key. |
Resolution: None. |
SV-TP-10209 WARNING | Internal | Failed to construct request instance. |
Cause: Failed to construct request instance. | - |
Resolution: Contact N-Squared support. |
SV-TP-10210 WARNING | Message | Encode Error: %s |
Cause: Failed to encode request bytes. |
%s = The result that occurred when trying to encode the request bytes. |
Resolution: Review the associated error result. Check message content construction. |
SV-TP-10212 ALARM | Connection | Closing persistent connection to %s after send request error: %s |
Cause: Persistent connection closed due to request send error. |
%s = The remote IPs/port. %s = The result that occurred when trying to send the request. |
Resolution: Review the associated error result. Review request message content construction. Check if the remote application is accepting requests. |
SV-TP-10212 CLEAR | Connection | Connection to %s restored. |
Cause: Connection usable again after closure due to request send error. |
%s = The remote IPs/port. |
Resolution: None. |
SV-TP-10214 ALARM | Connection | Closing persistent connection to %s after send response error: %s |
Cause: Persistent connection closed due to response send error. |
%s = The remote IPs/port. %s = The error result that occurred when trying to send the response. |
Resolution: Review the associated error result. |
SV-TP-10214 CLEAR | Connection | Connection to %s restored. |
Cause: Connection usable again after closure due to response send error. |
%s = The remote IPs/port. |
Resolution: None. |
SV-TP-10215 WARNING | Connection | Closing transient connection to %s after send request error: %s |
Cause: Transient connection closed due to request send error. |
%s = The remote IPs/port. %s = The result that occurred when trying to send the request. |
Resolution: Review the associated error result. Review request message content construction. Check if the remote application is accepting requests. |
SV-TP-10216 WARNING | Connection | Closing transient connection to %s after send response error: %s |
Cause: Transient connection closed due to response send error. |
%s = The remote IPs/port. %s = The error result that occurred when trying to send the response. |
Resolution: Review the associated error result. |
SV-TP-10217 WARNING | Message | Failed to send response to %s: %s |
Cause: Failed to send response message. |
%s = The remote IPs/port. %s = The error result that occurred when trying to send the response. |
Resolution: Review the associated error result. |
SV-TP-10218 WARNING | Message | Failed to send request to %s: %s. |
Cause: Failed to send request. |
%s = The remote IPs/port. %s = The result that occurred when trying to send the request. |
Resolution: Review the associated error result. Review request message content construction. Check if the remote application is accepting requests. |
SV-TP-10300 WARNING | Message | Failed to send response: %s |
Cause: Failed to send TCP response. |
%s = The error reason that the response could not be sent. |
Resolution: Review the associated error reason. |
SV-AP-10001 NOTICE | Configuration | Using localised authentication key '%s' for SNMP v3 messages for engine ID '%s' and user ID '%s'. |
Cause: Notification of the localised SNMP v3 authentication key generated from a plaintext password. For strict compatibility with SNMP v3, authentication keys should be configured instead of passwords. |
%s = The localised key that will be used for SNMP v3 authentication. %s = The SNMP engine ID used to generate the authentication key. %s = The SNMP user ID the authentication key belongs to. |
Resolution: None. |
SV-AP-10011 NOTICE | Configuration | Using localised privacy key '%s' for SNMP v3 messages for engine ID '%s' and user ID '%s'. |
Cause: Notification of the localised SNMP v3 privacy key generated from a plaintext password. For strict compatibility with SNMP v3, privacy keys should be configured instead of passwords. |
%s = The localised key that will be used for SNMP v3 encryption. %s = The SNMP engine ID used to generate the privacy key. %s = The SNMP user ID the privacy key belongs to. |
Resolution: None. |
SV-TP-10500 WARNING | Message | UDP Datagram sent only %d of %d bytes. Datagram was truncated. |
Cause: Mis-formed UDP datagram detected. |
%d = The number of bytes that were written via UDP. %d = The total number of bytes contained in the full datagram. |
Resolution: Review the message content construction. Inspect the UDP datagram payload. |
SV-TP-10506 WARNING | Message | Received invalid SCTP notification with length %d < 8. |
Cause: Received invalid SCTP notification. |
%d = The received notification length. |
Resolution: Contact N-Squared support. |
SV-TP-10507 WARNING | Message | Received invalid SCTP notification with length %d != sn_length %d. |
Cause: Received invalid SCTP notification. |
%d = The received notification length. %d = The notification length, as indicated in the notification. |
Resolution: Contact N-Squared support. |
SV-TP-10508 WARNING | Message | Received invalid SCTP_ASSOC_CHANGE notification with length %d < 20. |
Cause: Received invalid SCTP association change notification. |
%d = The received association change notification length. |
Resolution: Contact N-Squared support. |
SV-TP-10509 WARNING | Message | Invalid argument sending %d byte UDP Datagram to %s:%d. |
Cause: Failed to send UDP datagram with invalid attribute. Presumably bad destination address/port. |
%d = The datagram size in bytes. %s = The destination IPv4 address. %d = The destination UDP port number. |
Resolution: Review UDP datagram size, destination, and network routing parameters. |
SV-TP-10510 NOTICE | Connection | SCTP connection is now %s. |
Cause: SIGTRAN SCTP connection has been restarted from the far end. This indicates that the far-end lost and restored contact, prior to this end having noticed that the connection association was fully lost. |
%s = The new SCTP state (RESTART). |
Resolution: None. |
SV-TP-10511 WARNING | Message | Received unsupported SCTP_ASSOC_CHANGE notification. Flags = 0x%x. Length = %d. State = %d. Error = %d. OB Streams = %d. IB Streams = %d. Assoc ID = %d. |
Cause: Received unsupported SCTP association change notification. |
%x = The received association change notification's flags. %d = The received association change notification's length. %d = The received association change notification's [unsupported] state. %d = The received association change notification's error. %d = The received association change notification's outbound stream count. %d = The received association change notification's inbound stream count. %d = The received association change notification's association ID. |
Resolution: Contact N-Squared support. |
SV-TP-10512 WARNING | Message | Received invalid SCTP_PEER_ADDR_CHANGE notification with length %d != 148. |
Cause: Received invalid SCTP peer address change notification. |
%d = The received peer address change notification length. |
Resolution: Contact N-Squared support. |
SV-TP-10513 WARNING | Connection | SCTP connection peer [%s] state is now DOWN (%s). |
Cause: SIGTRAN SCTP connection peer is down (unreachable or potentially failed). Note that each SCTP connection may have multiple peers, and the connection communication will function as long as one or more other peers are still up. |
%s = The peer address description. %s = The peer status (UNREACHABLE/POTENTIALLY_FAILED). |
Resolution: Check network connectivity and connection parameters. |
SV-TP-10514 NOTICE | Connection | SCTP connection peer [%s] is now UP (%s). |
Cause: SIGTRAN SCTP connection peer is up (available or confirmed). |
%s = The peer address description. %s = The peer status (AVAILABLE/CONFIRMED). |
Resolution: None. |
SV-TP-10515 WARNING | Message | Received unexpected SCTP notification. Type = %d. Length = %d. Flags = 0x%x. SN Length = %d. |
Cause: Received unexpected SCTP notification. |
%d = The received notification type. %d = The received notification length. %x = The flags for the received notification. %d = The received notification SN length. |
Resolution: Contact N-Squared support. |
SV-TP-10516 WARNING | Message | Invalid message size sending %d byte UDP Datagram to %s:%d. |
Cause: Failed to send UDP datagram with invalid size. Presumably exceeded MTU for route. |
%d = The datagram size in bytes. %s = The destination IPv4 address. %d = The destination UDP port number. |
Resolution: Review UDP datagram size, destination, and network routing parameters. |
SV-TP-10518 ALARM | Connection | %s %s connection (local %s, remote %s) failed: %s |
Cause: Logged connection failed during connection attempt or after connecting. |
%s = Client/Server indicator. %s = Connection protocol UDP/TCP/SCTP. %s = The actual local IP:port values (or configured hostnames). %s = The actual remote IP:port values (or configured hostnames). %s = Connection failure reason. |
Resolution: Review socket, host, SSL configuration. |
SV-TP-10518 CLEAR | Connection | %s %s connection is ready. Local = %s, Remote = %s. |
Cause: A ClientConnection initiated by is now connected, meaning that the socket transport layer handshake is completed, and if applicable the SSL handshake is also complete. The application may now initiate any protocol-specific validation/login process. |
%s = Client/Server indicator. %s = The transport protocol TCP/SCTP/UDP %s = The actual local IP:port values. %s = The actual remote IP:port values. |
Resolution: None. |
SV-TP-10519 WARNING | Connection | %s %s connection (local %s, remote %s) failed: %s |
Cause: Non-logged connection failed during connection attempt or after connecting. |
%s = Client (connect) or Server (listen/accept) socket? %s = Connection protocol TCP/SCTP. %s = The actual local IP:port values (or configured hostnames). %s = The actual remote IP:port values (or configured hostnames). %s = Connection failure reason. |
Resolution: Review socket, host, SSL configuration. |
SV-TP-10520 ALARM | Connection | %s %s connection is congested. Local = %s, Remote = %s. |
Cause: Connection has become congested. |
%s = Client/Server indicator. %s = The transport protocol TCP/SCTP/UDP %s = The actual local IP:port values. %s = The actual remote IP:port values. |
Resolution: Adjust stream buffer size configuration, or reduce traffic on this connection. |
SV-TP-10520 CLEAR | Connection | %s %s connection is no longer congested. Local = %s, Remote = %s. |
Cause: Connection is no longer congested. This may be because the Connection has terminated. |
%s = Client/Server indicator. %s = The transport protocol TCP/SCTP/UDP %s = The actual local IP:port values. %s = The actual remote IP:port values. |
Resolution: None. |
SV-TP-11000 NOTICE | Connection | Creating UDP connection for %s |
Cause: Application startup. Creating single UDP connection. |
%s = The local host:port. |
Resolution: None. |
SV-TP-11007 ALARM | Connection | Error binding %s server: %s |
Cause: Socket bind failed. |
%s = Bind protocol. %s = Bind failure detailed message. |
Resolution: Review socket and host bind configuration. |
SV-TP-11007 CLEAR | Connection | Socket bind/listen succeeded for %s at %s. |
Cause: Socket bind & listen succeeded. |
%s = Protocol name. %s = Local connection point. |
Resolution: None. |
SV-TP-11008 WARNING | Connection | Error accepting SCTP on %s: %s |
Cause: Error accepting messages on local connection. |
%s = The configured local listen description. %s = The error message that occurred when trying to accept on the local connection. |
Resolution: Review the associated error result. |
SV-TP-11009 WARNING | Connection | Error accepting TCP connection: %s |
Cause: Failed to accept inbound TCP connection. |
%s = The error result when trying to accept inbound TCP connection. |
Resolution: Review the associated error result. |
SV-TP-11010 WARNING | Connection | Error creating new %s ServerConnection: %s |
Cause: Failed to process new inbound connection. |
%s = The protocol type for the stream connection TCP or SCTP. %s = The error result when trying to accept inbound connection. |
Resolution: Review the associated error result. |
SV-TP-11011 NOTICE | Connection | Accepted SCTP connection from remote IP address %s, remote port %s. |
Cause: Application startup. SCTP connection accepted connection from remote IP address. |
%s = The configured remote IP address. %s = The configured remote port. |
Resolution: None. |
SV-TP-10400 WARNING | Connection | SSL is not supported on '%s' connections. Ignored. |
Cause: SSL is not supported on non-TCP protocol (e.g. UDP). |
%s = The configured connection protocol. |
Resolution: Check application protocol and SSL configuration. |
SV-AP-10018 WARNING | Message | SNMP trap queue failed: %s. Trap detail: %s |
Cause: SNMP trap was not able to be queued for sending. |
%s = The reason for failure. %s = The trap details. |
Resolution: Check the error message and update configuration and/or implementation accordingly. |
SV-AP-10025 WARNING | Message | CLASS %s is missing 'trace_label()' method. |
Cause: An N2SVCD class is incorrectly specified. |
%s = The class name. |
Resolution: Contact N-Squared support. |
SV-AP-10065 NOTICE | Application | Suppressed a total of %d duplicate warnings [%s]. |
Cause: The same warning ID was logged too many times in a fixed interval. |
%d = The number of warnings that were suppressed. %s = The event ID of the suppressed warnings. |
Resolution: Address the underlying problem which caused the warnings. |
SV-AP-10010 WARNING | Configuration | SNMP App Name '%s' discovery failed: %s |
Cause: SNMP application discovery immediate failure. |
%s = The configured SNMP application name. %s = The reason for immediate failure. |
Resolution: Check global SNMP application name configuration. |
SV-AP-10022 NOTICE | Application Configuration | No SNMP user defined for outbound traps. No message security will be applied. |
Cause: No SNMP user is defined for outbound SNMP traps. Messages will be sent without security. | - |
Resolution: None. |
SV-AP-10026 WARNING | Message | Abandoning undeliverable queued SNMP trap from broker. Trap detail: %s |
Cause: Queued SNMP trap was discarded due to too many pending traps in the SNMP broker. |
%s = The trap details. |
Resolution: Increase the SNMP broker queue size. Ensure all N2SVCD applications start correctly. |
SV-AP-10027 WARNING | Message | Failed to encode queued SNMP v3 trap: %s. Trap detail: %s |
Cause: Queued SNMP v3 trap was was unable to be encoded. |
%s = The encoding result. %s = The trap details. |
Resolution: Contact N-Squared Support. |
SV-AP-10028 WARNING | Message | Failed to encode queued SNMP v2c trap: %s. Trap detail: %s |
Cause: Queued SNMP v2c trap was was unable to be encoded. |
%s = The encoding result. %s = The trap details. |
Resolution: Contact N-Squared Support. |
SV-AP-10036 WARNING | Message | SNMP application '%s' is not available, abandoning. Trap details: %s |
Cause: Target SNMP application is invalid or not available for outbound proxying of SNMP trap. Trap will not be sent. |
%s = The target application name. %s = The trap details. |
Resolution: Ensure SNMP applications are running without error. Check SNMP configuration. |
SV-AP-10037 WARNING | Message | Failed to pass SNMP trap for proxying, abandoning: %s. Trap details: %s |
Cause: SNMP trap was was unable to be passed to an SNMP application for outbound proxying. Trap will not be sent. |
%s = The target application name. %s = The trap details. |
Resolution: Review error message. Ensure SNMP applications are running without error. Check SNMP configuration. |
SV-AP-10055 WARNING | Message | Abandoning undeliverable queued SNMP trap from broker client. Trap detail: %s |
Cause: Queued SNMP trap was discarded due to too many pending traps in the SNMPb broker client. |
%s = The trap details. |
Resolution: Increase the SNMP broker queue size. Ensure all N2SVCD applications start correctly. |
SV-AP-10059 WARNING | Message | Discarding failed SNMP trap: %s. Trap detail: %s |
Cause: SNMP trap failed to send for a reason other than connection refused. The trap will be discarded. |
%s = The send result. %s = The trap details. |
Resolution: Review error message and update configuration accordingly. |
SV-SS-10000 NOTICE | Application | No handlers defined. Cannot handle inbound SOAP requests. |
Cause: Application startup. No inbound handlers are defined. | - |
Resolution: Review handler configuration. |
SV-SS-10000 NOTICE | Application | No handlers defined. Cannot handle inbound SOAP requests. |
Cause: Application startup. No inbound handlers are defined. | - |
Resolution: Review handler configuration. |
SV-SS-10001 NOTICE | Application | Add namespace within response message = %s. |
Cause: Parameter configuration at startup. Whether or not to add namespacing within response messages. |
%s = Whether or not to add namespaces to inner response elements. |
Resolution: None. |
SV-SS-10001 NOTICE | Application | Add namespace within response message = %s. |
Cause: Parameter configuration at startup. Whether or not to add namespacing within response messages. |
%s = Whether or not to add namespaces to inner response elements. |
Resolution: None. |
SV-SS-10002 NOTICE | Application | Compatibility = '%s'. |
Cause: Parameter configuration at startup. The compatibility mode. |
%s = The current quirks mode. |
Resolution: None. |
SV-SS-10002 NOTICE | Application | Compatibility = '%s'. |
Cause: Parameter configuration at startup. The compatibility mode. |
%s = The current quirks mode. |
Resolution: None. |
SV-SS-10008 NOTICE | Application | Output Mode = '%s'. |
Cause: Parameter configuration at startup. The output mode. |
%s = The current output mode. |
Resolution: None. |
SV-SS-10008 NOTICE | Application | Output Mode = '%s'. |
Cause: Parameter configuration at startup. The output mode. |
%s = The current output mode. |
Resolution: None. |
SV-SS-10009 NOTICE | Application | Add namespace to array items = %s. |
Cause: Parameter configuration at startup. Whether or not to add namespaces to array items. |
%s = Whether or not to add namespaces to array items. |
Resolution: None. |
SV-SS-10009 NOTICE | Application | Add namespace to array items = %s. |
Cause: Parameter configuration at startup. Whether or not to add namespaces to array items. |
%s = Whether or not to add namespaces to array items. |
Resolution: None. |
SV-SS-10003 WARNING | Message | Cannot queue response: %s |
Cause: Failed to send SOAP fault response. |
%s = The error result when sending the response. |
Resolution: Review the associated error result. |
SV-SS-10004 WARNING | Connection | Duplicate request received for in-progress Instance. Discarded! |
Cause: Received duplicate request for in progress instance. Request discarded. | - |
Resolution: Contact N-Squared support. |
SV-SS-10005 NOTICE | Job | Timeout performing local processing. Far end abandoned. |
Cause: Client abandoned its connection to us. Cleaning up. | - |
Resolution: None. |
SV-SS-10006 NOTICE | Job | Timeout performing local processing. Reply with 504 Gateway Timeout. |
Cause: Reached the 504 gateway timeout limit. Sending 504 response to client. | - |
Resolution: None. |
Statistics
The following 29 statistics may be generated by N2SVCD Application “SoapServerApp”.
No statistics found that match search criteria.
instance.count | Type: | Gauge | Scope: | Job | OID: | - |
Cause: | The number of open application instances. Depending on the application, an "instance" may represent a transaction, call, session, request/response pair, etc. |
instance.throttle.max_instances | Type: | Counter | Scope: | Message | OID: | - |
Cause: | Maximum number of instances exceeding the max number of instances. |
instance.throttle.max_tps_average | Type: | Counter | Scope: | Message | OID: | - |
Cause: | Average max TPS for the last throttle period. |
snmp.msg.proxy | Type: | Counter | Scope: | Message | OID: | 1.3.6.1.4.1.56540.2.1.1.1 |
Cause: | Proxied SNMP requests received from an SNMP app. Note that only (some) request-type SNMP PDUs are sent to applications. |
Tags: | type |
get |
Internal requests received from an SNMP get-request PDU. | next |
Internal requests received from an SNMP get-next-request PDU. | bulk |
Internal requests received from an SNMP get-bulk-request PDU. | set |
Internal requests received from an SNMP set-request PDU. | other |
Internal requests received from other SNMP PDUs. |
instance.abort | Type: | Counter | Scope: | Job, Message | OID: | - |
Cause: | Application instances aborted due to receiving an unexpected shutdown/abort message. Depending on the application, an "instance" may represent a transaction, call, session, request/response pair, etc. Note that aborted instances are still counted in instance.shutdown. |
instance.shutdown | Type: | Counter | Scope: | Job, Message | OID: | - |
Cause: | Application instances shut down (for any reason, including abort). Depending on the application, an "instance" may represent a transaction, call, session, request/response pair, etc. |
instance.start | Type: | Counter | Scope: | Job, Message | OID: | - |
Cause: | Application instances started. Depending on the application, an "instance" may represent a transaction, call, session, request/response pair, etc. |
send.request.cancel | Type: | Counter | Scope: | Message | OID: | - |
Cause: | Sent requests cancelled. |
Tags: | reason |
abandon |
Outbound messages abandoned due to send failure(s). | offline |
Outbound messages not sent due to client being offline. |
send.request.retry | Type: | Counter | Scope: | Job, Message | OID: | - |
Cause: | Outbound messages retrying after timeout or disconnection. |
token.request | Type: | Counter | Scope: | Job, Message | OID: | - |
Cause: | Made token request to the token client application. |
token.response.error | Type: | Counter | Scope: | Message | OID: | - |
Cause: | Token response errors for tokens sent to other applications. |
Tags: | type |
timeout |
Failed to receive token response to the token client application in time. | declined |
Token request was declined/invalid from the far end. |
token.response.success | Type: | Counter | Scope: | Job, Message | OID: | - |
Cause: | Token request was declined/invalid from the far end. |
connection.connect | Type: | Counter | Scope: | Connection | OID: | - |
Cause: | TCP connections ready for use. |
connection.disconnect | Type: | Counter | Scope: | Connection | OID: | - |
Cause: | TCP connections disconnected (including failed connection attempts). |
connection.error.parse | Type: | Counter | Scope: | Job, Message | OID: | - |
Cause: | TCP requests or responses that could not be parsed. |
receive.request | Type: | Counter | Scope: | Message | OID: | - |
Cause: | TCP/UDP requests received. |
Tags: | proto |
tcp |
Requests received over TCP. | udp |
Requests received over UDP. |
type |
user |
Requests received for user messages. | proto |
The protocol of the network connection (TCP/UDP). | bad_key |
Requests received with no correlation key. | duplicate |
Requests received that are already being processed. | no_instance |
Requests received that failed to construct an instance. | error |
Requests received that failed to be processed successfully. | ping |
Ping requests received. | login |
Login requests received. |
receive.response | Type: | Counter | Scope: | Message | OID: | - |
Cause: | TCP/UDP responses received. |
Tags: | proto |
tcp |
Requests received over TCP. | udp |
Requests received over UDP. |
type |
user |
Responses received for user messages. | bad_key |
Responses received with no correlation key. | no_req_async |
Responses received asynchronously without matching request. | no_req_sync |
Responses received synchronously without matching request. | ping |
Ping responses received. | login |
Login responses received. |
send.request | Type: | Counter | Scope: | Job, Message | OID: | - |
Cause: | TCP/UDP requests prepared to be sent. |
Tags: | proto |
tcp |
Requests sent over TCP. | udp |
Requests sent over UDP. |
send.request.error | Type: | Counter | Scope: | Message | OID: | - |
Cause: | TCP/UDP requests not sent successfully. |
Tags: | proto |
tcp |
Requests received over TCP. | udp |
Requests received over UDP. |
type |
encode |
Requests that could not be encoded. | stream |
Requests that could not be sent. | timeout |
Requests that timed out on send. |
send.response | Type: | Counter | Scope: | Job, Message | OID: | - |
Cause: | TCP/UDP responses prepared to be sent. |
Tags: | proto |
tcp |
Responses sent over TCP. | udp |
Responses sent over UDP. |
send.response.error | Type: | Counter | Scope: | Message | OID: | - |
Cause: | TCP/UDP responses not sent successfully. |
Tags: | proto |
tcp |
Requests received over TCP. | udp |
Requests received over UDP. |
type |
encode |
Responses that could not be encoded. | stream |
Responses that could not be sent. |
send.unsent.error.timeout | Type: | Counter | Scope: | Job, Message | OID: | - |
Cause: | TCP/UDP requests or responses that timed out on send. |
Tags: | proto |
tcp |
Requests received over TCP. | udp |
Requests received over UDP. |
soap.request | Type: | Counter | Scope: | Message | OID: | - |
Cause: | SOAP requests received. Does not include unparseable requests. |
soap.request | Type: | Counter | Scope: | Message | OID: | - |
Cause: | SOAP requests received. Does not include unparseable requests. |
soap.request.invalid | Type: | Counter | Scope: | Message | OID: | - |
Cause: | Invalid SOAP requests received. |
Tags: | type |
no_action |
SOAP requests received without a SOAPAction header. | no_content_type |
SOAP requests received without a Content-Type header. | content_type |
SOAP requests received with an unsupported Content-Type header. | xml |
SOAP requests received with XML that cannot be parsed. | no_envelope |
SOAP requests received without a SOAP Envelope. | no_ns_envelope |
SOAP requests received with a SOAP Envelope without a namespace. | ns_envelope |
SOAP requests received with an invalid SOAP Envelope namespace. | no_body |
SOAP requests received without a SOAP Body. | no_message |
SOAP requests received without an element within the SOAP Body. | multi_message |
SOAP requests received with multiple elements within the SOAP Body. | no_msg_name |
SOAP requests received without a message name. | ns_param_unknown |
SOAP requests received containing an unknown parameter namespace. | ns_param_no_match |
SOAP requests received containing a parameter namespace that does not match the result namespace. |
soap.request.invalid | Type: | Counter | Scope: | Message | OID: | - |
Cause: | Invalid SOAP requests received. |
Tags: | type |
no_action |
SOAP requests received without a SOAPAction header. | no_content_type |
SOAP requests received without a Content-Type header. | content_type |
SOAP requests received with an unsupported Content-Type header. | xml |
SOAP requests received with XML that cannot be parsed. | no_envelope |
SOAP requests received without a SOAP Envelope. | no_ns_envelope |
SOAP requests received with a SOAP Envelope without a namespace. | ns_envelope |
SOAP requests received with an invalid SOAP Envelope namespace. | no_body |
SOAP requests received without a SOAP Body. | no_message |
SOAP requests received without an element within the SOAP Body. | multi_message |
SOAP requests received with multiple elements within the SOAP Body. | no_msg_name |
SOAP requests received without a message name. | ns_param_unknown |
SOAP requests received containing an unknown parameter namespace. | ns_param_no_match |
SOAP requests received containing a parameter namespace that does not match the result namespace. |
soap.request.parse_fail | Type: | Counter | Scope: | Message | OID: | - |
Cause: | SOAP requests received that could not be parsed. |
Tags: | type |
bad_header |
SOAP requests received with HTML headers that cannot be parsed. | bad_length |
SOAP requests received with invalid delimited content. | bad_chunk |
SOAP requests received with invalid chunked content. |
soap.request.parse_fail | Type: | Counter | Scope: | Message | OID: | - |
Cause: | SOAP requests received that could not be parsed. |
Tags: | type |
bad_header |
SOAP requests received with HTML headers that cannot be parsed. | bad_length |
SOAP requests received with invalid delimited content. | bad_chunk |
SOAP requests received with invalid chunked content. |
soap.request.error | Type: | Counter | Scope: | Message | OID: | - |
Cause: | Unhandled SOAP requests received. |
Tags: | type |
no_handler |
Requests received not claimed by a handler. | bad_handler |
Requests received assigned to an invalid handler. | handover |
Requests received unable to be passed to a handler. |