Jump to: navigation, search

Interaction Server

This page lists changes to Interaction Server log events after release 8.5.000.10. Log events for releases 8.5.000.10 and earlier are described in Combined Log Events Help.

In the Text field, expressions %s and %d represent text (%s) or numeric (%d) values that are filled in according to the actual context that generates the message. The Attributes field identifies them with parenthesized numbers that correspond to the order they occur in the text. For example, for 01-21032 immediately below, (1) is the first %s, (2) is the only %d, and (3) is the second %s.

Important
Interaction Server supports two application types in the Configuration Server database: T-Server and Interaction Server. When launched in Interaction Server mode, the log events all have the prefix 111-, as shown here. When launched in T-Server mode, the event has the prefix 01-, but the five digits after the hyphen are the same as those listed here

Release 8.5.300

New

111-55019

Level STANDARD
Text '%s' is above threshold, current value: '%d", maximum value: '%d'
Attributes (1) Name of KPI counter

(2) Current value of KPI counter
(3) Current value of KPI counter threshold

Description The server detects that a KPI counter is above a predefined threshold and logs the current KPI counter value versus the predefined threshold.
Actions None
Alarm Advisory Indicates abnormal condition and can be used to set an alarm.

Release 8.5.201

New

111-30005

Level STANDARD
Text Primary mode activated...
Attributes None
Description The server is ready to process client requests after switchover or startup.
Actions None
Alarm Advisory None

Release 8.5.110

New

111-55017

Level TRACE
Text Current license usage: agent seat: %d/%d, email: %d/%d, chat: %d/%d, SMS: %d/%d, open media: %d/%d
Attributes Each pair of numbers is number of licenses in use / total allocated.
Description For each license type, actual license usage versus license allocation.
Actions None
Alarm Advisory None

111-23411

Level STANDARD
Text The maximum user data size (%d - limit) is exceeded (%d - actual) for interaction '%s' while processing request '%s' from client %d:%d, reference id: %d
Attributes (1) Maximum limit set in bytes

(2) The actual size of packed user data
(3) Interaction identifier
(4) The name of the request being processed
(5) The server-generated client identifier
(6) The connection ID of the client
(7) Reference ID of the request

Description The server detects that the user data provided in RequestSubmit or resulting user data size after processing of RequestChangeProperties is greater than the set limit.
Actions None
Alarm Advisory None

111-25097

Level TRACE
Text Moving '%d' interactions into cache, using '%s'
Attributes (1) Number of interactions to be moved into cache

(2) The condition for the specific segment

Description While processing the segmentation view, the server detects that it has to move the specified number of interactions into the cache.
Actions None
Alarm Advisory None

111-25098

Level TRACE
Text Segmented view queue: '%s', Segments: '%d', Total available: '%d', Total cached: '%d':%s
Attributes (1) Interaction Queue name

(2) Number of different segments present in the database
(3) Number of interactions that can be potentially moved to cache
(4) Number of interactions already cached
(5) Detailed information about each segment (possibly limited)

Description Provides detailed information about the segmentation process, including the total number of potential interactions and number of interactions for each segment currently present in the database.
Actions None
Alarm Advisory None

111-66000

Level STANDARD
Text Event logger Groovy '%s': JVM is not available
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)
Description The event logger could not initialize JVM
Actions None
Alarm Advisory None

111-66001

Level STANDARD
Text Event logger Groovy '%s': Initialization has failed
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)
Description The event logger could not initialize for some reason. Additional log messages should indicate the reason.
Actions None
Alarm Advisory None

111-66002

Level STANDARD
Text Event logger Groovy '%s': Queue size reached, discarding events
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)
Description The event logger could not process the entire stream of reporting events and reached the maximum event queue size. The accumulated events will be discarded.
Actions None
Alarm Advisory None

111-66004

Level STANDARD
Text Event logger Groovy '%s': Cannot flush on shutdown, JVM is not available
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)
Description The event logger could not process the event queue on shutdown.
Actions None
Alarm Advisory None

111-66005

Level STANDARD
Text Event logger Groovy '%s': Shutdown has failed
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)
Description The event logger could not shut down properly
Actions None
Alarm Advisory None

111-66009

Level STANDARD
Text Event logger Groovy '%s': Settings refresh has failed
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)
Description Error has occurred on event logger settings refresh
Actions None
Alarm Advisory None

111-66011

Level TRACE
Text Event logger Groovy '%s': Exception message: %s
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)

(2) Exception message

Description Exception has occurred.
Actions None
Alarm Advisory None

111-66013

Level TRACE
Text Event logger Groovy '%s': Event is not written, filtered by activity: activity: '%s'
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)

(2) Activity name

Description Error has occurred on event logger settings refresh
Actions None
Alarm Advisory None

111-66014

Level TRACE
Text Event logger Groovy '%s': Custom event is not written to the table, required attributes are absent, custom_eventid: '%d'
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)

(2) Custom event ID

Description Custom event lacks next required attributes.
Actions None
Alarm Advisory None

111-66015

Level TRACE
Text Event logger Groovy '%s' started
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)
Description This groovy event logger has started.
Actions None
Alarm Advisory None

111-66016

Level STANDARD
Text Event logger Groovy '%s': Failed to load %s class
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)

(2) Class name

Description Cannot load this class.
Actions None
Alarm Advisory None

111-66017

Level STANDARD
Text Event logger Groovy '%s': Failed to create global reference to %s class
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)

(2) Class name

Description Cannot create global reference to this class using JNI
Actions None
Alarm Advisory None

111-66018

Level STANDARD
Text Event logger Groovy '%s': Failed to get %s method id in %s class
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)

(2) Method name
(3) Class name

Description Cannot find method in class using JNI
Actions None
Alarm Advisory None

111-66019

Level STANDARD
Text Event logger Groovy '%s': Failed to create instance of %s class
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)

(2) Class name

Description Cannot create instance of class using JNI
Actions None
Alarm Advisory None

111-66020

Level STANDARD
Text Event logger Groovy '%s': Failed to register %s class native methods
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)

(2) Class name

Description Error on registration of native methods of a class
Actions None
Alarm Advisory None

111-66021

Level STANDARD
Text Event logger Groovy '%s': %s class method %s has failed
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)

(2) Class name
(3) Method name

Description Class method has failed
Actions None
Alarm Advisory None

111-66022

Level STANDARD
Text Event logger Groovy '%s': Failed to allocate Java 'String' with logger name
Attributes (1) Logger name as defined in configuration (application name of the event logger DAP)
Description Cannot allocate string that contains event logger object name using JNI
Actions None
Alarm Advisory None

111-66101

Level TRACE
Text  %s
Attributes (1) Message string
Description Trace message
Actions None
Alarm Advisory None

111-66102

Level Standard
Text  %s
Attributes (1) Message string
Description Standard message
Actions None
Alarm Advisory None

111-66200

Level Standard
Text Configuration option '%s' value ('%s') must be between '%s' and '%s'
Attributes (1) Option name

(2) Option value
(3) Minimum value
(4) Maximum value

Description Configuration option value doesn't fit into specified range
Actions None
Alarm Advisory None

111-66201

Level Standard
Text Configuration option '%s' value ('%s') exceeds type max value of '%s', max value will be used
Attributes (1) Option name

(2) Option value
(3) Maximum type value

Description Configuration option value doesn't fit into standard type range (Integer, Long, BigDecimal, etc), max type value will be used (Integer.MAX_VALUE, etc)
Actions None
Alarm Advisory None

Release 8.5.109 and Earlier

New

111-21032

Level TRACE
Text Loaded enhanced strategy configuration, enhanced strategy name: '%s', tenant id: '%d', state: %s
Attributes (1) The name of the strategy script
(2) The configuration DBID of the tenant
(3) Configuration object state (enabled/disabled)
Description The server has loaded information about enhanced strategy script from configuration
Actions None
Alarm Advisory None

111-23088

Level TRACE
Text The strategy '%s' (tenant '%d') does not exist; while processing request '%s' from client %d:%d, reference id: %d
Attributes (1) The name of the strategy script
(2) The configuration DBID of the tenant
(3) The name of the request being processed
(4) The server generated client identifier
(5) The connection ID of the client
(6) Reference ID of the request
Description The strategy name specified in the pull request does not exist in the configuration.
Actions Check the client configuration for the correct strategy name.
Alarm Advisory None

111-23089

Level TRACE
Text The strategy '%s' (tenant '%d') has not enabled views; while processing request '%s' from client %d:%d, reference id: %d
Attributes (1) The name of the strategy script
(2) The configuration DBID of the tenant
(3) The name of the request being processed
(4) The server generated client identifier
(5) The connection ID of the client
(6) Reference ID of the request
Description The strategy specified in the pull request does not have any Interaction Views associated with it.
Actions Check business process configuration and associate the strategy with the required Interaction View/Interaction Queue
Alarm Advisory None

111-23090

Level TRACE
Text The strategy '%s' (tenant '%d') is disabled; while processing request '%s' from client %d:%d, reference id: %d
Attributes (1) The name of the strategy script
(2) The configuration DBID of the tenant
(3) The name of the request being processed
(4) The server generated client identifier
(5) The connection ID of the client
(6) Reference ID of the request
Description The strategy specified in the pull request is disabled.
Actions None
Alarm Advisory None


111-23091

Level STANDARD
Text View pull manager for '%lu:%s': database select request timeout out
Attributes (1) The configuration DBID of the tenant
(2) The name of the Interaction View
Description The select request generated for the specified View took longer than configured database request timeout.
Actions Ensure efficiency of the generated select statement by simplifying logic and/or adding appropriate indexes.
Alarm Advisory None


111-23092

Level TRACE
Text Pull failed due to an error in the condition or the order of a view ; while processing request '%s' from client %d:%d, reference id: %d
Attributes (1) The name of the request being processed
(2) The server generated client identifier
(3) The connection ID of the client
(4) Reference ID of the request
Description The Interaction View configuration contains a syntax error in the condition or in the order.
Actions Correct the View configuration according to more detailed error messages from the database.
Alarm Advisory None

111-23375

Level TRACE
Text Due to '%s' option settings, place_id '%s' has been overrided with agent_id '%s'
Attributes (1) The option name
(2) The name of the place received in the login request
(3) The agent ID specified in the request
Description The server is configured to limit the ability of agents to log in to different places
Actions None
Alarm Advisory None

111-23376

Level TRACE
Text Due to '%s' option settings, agent_id is mandatory field which has not been provided
Attributes (1) The option name
Description The server is configured to limit the ability of agents to log in to different places. In this mode, the specification of the agent ID in the login request is mandatory
Actions None
Alarm Advisory None

111-23377

Level STANDARD
Text All %d capture points function properly
Attributes (1) Number of configured capture points
Description The server indicates that all capture points are functioning properly
Actions None
Alarm Advisory This message can be used to reset the alarm initiated by 23378

111-23378

Level STANDARD
Text Only %d out of %d capture points function properly
Attributes (1) Number of active capture points
(2) Number of configured capture points
Description The server indicates that not all capture points are functioning properly
Actions Check configuration and connectivity for all capture points
Alarm Advisory Indicates abnormal condition and can be used to set an alarm. The correct Cancel Event is 23377

111-23400

Level TRACE
Text Agent '%s' at place '%s' of tenant '%s' (id: %d) has already accepted an invitation (%d) to handle interaction '%s', while processing request '%s' from client %d:%d, reference id: %d
Attributes (1) The agent ID
(2) The place name
(3) The tenant name
(4) The configuration DBID of the tenant
(5) The invitation ticket ID
(6) The interaction ID
(7) The name of the request being processed
(8) The server generated client identifier
(9) The connection ID of the client
(10) Reference ID of the request
Description The server indicates that agent has already accepted an invitation to handle the specified interaction and no error response has been generated to the agent application
Actions None
Alarm Advisory None

111-23401

Level TRACE
Text Could not load file '%s', default metadata will be provided
Attributes (1) The file name of the metadata file
Description The server could not load the specified metadata file and will provide the default metadata instead
Actions None
Alarm Advisory None

111-23402

Level TRACE
Text Could not parse file '%s', default metadata will be provided, error code: '%d', error message: '%s'
Attributes (1) The file name of the metadata file
(2) The error code of the XML parser
(3) The error message of the XML parser
Description The server could not parse the specified XML file and will provide the default metadata instead
Actions None
Alarm Advisory None

111-23403

Level TRACE
Text Health metadata successfully loaded from file '%s'
Attributes (1) The file name of the metadata file
Description The server has loaded and parsed the metadata file and will provide the loaded metadata to clients
Actions None
Alarm Advisory None

111-23404

Level TRACE
Text Connection string build: Multiple ODBC connection strings are present. In '%s' from section '%s' ignoring option '%s': %s
Attributes (1) The application name
(2) The section name
(3) The option name
(4) The option value
Description The specified ODBC option is found, but its value is not used
Actions None
Alarm Advisory None

111-23406

Level TRACE
Text ODBC connection string has been built: %s
Attributes (1) The connection string
Description The ODBC connection string has been built
Actions None
Alarm Advisory None

111-23409

Level TRACE
Text Error/request counting facility enabled [%s]
Attributes (1) The list of KPI counters group names
Description The server will collect KPI counters for specified counter groups related to number of requests, ESP requests and errors types
Actions None
Alarm Advisory None

111-23410

Level TRACE
Text Error/request counting facility disabled
Attributes None
Description The server will not collect KPI counters related to number of requests, ESP requests and errors types
Actions None
Alarm Advisory None

111-25067

Level STANDARD
Text Unknown delivery protocol '%s' specified for event logger '%s'
Attributes (1) The protocol name specified for the event logger
(2) The event logger name (DAP name)
Description An unexpected value is specified for the event logger type (delivery protocol for reporting events).
Actions Check option 'delivery-protocol' and specify one of the supported types
Alarm Advisory None

111-25068

Level STANDARD
Text Failed to initialize event logger '%s' (delivery protocol '%s')
Attributes (1) The event logger name (DAP name)
(2) The protocol name specified for the event logger
Description The server could not initialize the event logger
Actions None
Alarm Advisory None

111-25069

Level STANDARD
Text Event logger configuration error: DAP '%s', DB Server information required
Attributes (1) The event logger name (DAP name)
Description The specified event logger requires a connection to DB Server
Actions None
Alarm Advisory None

111-25095

Level TRACE
Text View '%lu:%s': flushing the cache back to queue, reason: no consumers
Attributes (1) The tenant DBID
(2) The Interaction View name
Description The server drops all the interactions cached for the specified View due to 1 minute timeout
Actions None
Alarm Advisory None

111-26025

Level TRACE
Text ...distributing message '%s' to %d more clients ('%s')
Attributes (1) The protocol message name
(2) Number of additional clients
(3) The list of clients
Description The server distributes the specified protocol message (usually a reporting event) to the specified clients
Actions None
Alarm Advisory None

111-26108

Level TRACE
Text Cannot register client, this routing engine name is already registered, client %d:%d, name: %s
Attributes (1) The client identifier
(2) The connection identifier
(3) The name of the client
Description The server denies client registration to routing engine (including, possibly, URS) due to the fact that there is already a connection from the same application
Actions None
Alarm Advisory None

111-26450

Level TRACE
Text New client %d connected on port %d
Attributes (1) The connection identifier
(2) The port number
Description The server accepted a client connection
Actions None
Alarm Advisory None

Changed

The following log event messages were changed.

01-23075

Level TRACE
Previous Text Failed to translate statement '%s', at position %d, reason: %s
New Text Failed to translate statement '%s' in view '%s', at position %d, reason: %s
New Attribute (2) - The name of the interaction View for which the condition or order is being prepared


01-23353

Level TRACE
Previous Text Capture point '%s': Connected DAP '%s' engine '%s' is not supported.
New Text Connection string build: Engine '%s' from DAP '%s' is not supported.
New Attribute (1) - The name of the database capture point for which the connection string is being constructed


01-23354

Level TRACE
Previous Text Capture point '%s': Engine '%s' from DAP '%s' was added as driver '%s' into DB connection string.
New Text Connection string build: Engine '%s' from DAP '%s' was added as a driver '%s' into ODBC connection string.
New Attribute (1) - The name of the database capture point for which the connection string is being constructed


01-23356

Level TRACE
Previous Text Capture point '%s': Problem with parsing following value during connection-string builiding: '%s'
New Text Problem with parsing following value during connection-string builiding: '%s'
New Attribute (1) - The name of the database capture point for which the connection string is being constructed


01-26201

Level TRACE
Previous Text Third party server response received from '%s' at host '%s', port %d, connection %d, reference id %d, data:%s%suser data:%s%s
New Text Received ESP response message '%s' ('%d') from client '%s' - %s:%d, current queue size: %d, message attributes:%s%s
New Attribute (1) - The name of the protocol message received.
(2) - The ID of the message received.
(6) - The number of currently queued ESP requests to the ESP server from which the response is received.


01-26202

Level TRACE
Previous Text Sending third party server request to '%s' at host '%s', port %d, connection %d, reference id %d:%s%s
New Text Sending third party server request to '%s' at host '%s', port %d, connection %d, reference id %d, current queue size: %d:%s%s
New Attribute (6) - The number of currently queued ESP requests to the specified ESP server.


01-55014

Level TRACE
Previous Text Closing server port (connection %d)...
New Text Closing server port, connection %d, port %d...
New Attribute (2) - The number of the port being closed


01-55015

Level TRACE
Previous Text Server port has been closed (connection %d)...
New Text Server port has been closed, connection %d, port %d...
New Attribute (2) - The number of the port that was closed


Removed

The following log event messages were removed.

Number Level Text
01‑23013 TRACE Database failure while processing request '%s' from client %d:%d, reference id: %d
01-23030 TRACE Database request has failed while processing request '%s' from client %d:%d, reference id: %d
01-23110 TRACE Database request has failed while processing request '%s' from client %d:%d, reference id: %d
01-26203 TRACE Third party server fault received from '%s' at host '%s', port %d, connection %d, reference id %d, data:%s%s
01-26205 TRACE Received third party server request from client, connection %d, reference id %d, data:%s%suser data:%s%s

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on October 15, 2018, at 06:47.