Cisco Cisco Customer Voice Portal Downloads 发行公告
C
HAPTER
5:
VXML Server
L
OGGING
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
94
The Global Error Logger
The Global Error Logger records errors that occur outside the realm of a particular application.
Application-level errors are logged by application-level loggers, which are described later in this
chapter. Another type of error that the Global Error Logger receives is an application-level error
that encountered trouble with its logging. In order to prevent the loss of the data, VXML Server
activates a global logger event with the original application error as a backup.
Application-level errors are logged by application-level loggers, which are described later in this
chapter. Another type of error that the Global Error Logger receives is an application-level error
that encountered trouble with its logging. In order to prevent the loss of the data, VXML Server
activates a global logger event with the original application error as a backup.
The error log file names are in the form “error_logYYYY-MM-DD.txt” where YYYY, MM, and
DD are the year, month, and day when the error log was first created. By default, the log folder is
named “GlobalErrorLogger” (though the name is set in the
DD are the year, month, and day when the error log was first created. By default, the log folder is
named “GlobalErrorLogger” (though the name is set in the
global_config.xml
file and can be
changed by the administrator). Global error log files are rotated daily. Note that if no error
occurred on a particular day, no error log will be created. The file is organized in a comma-
delimited format with 2 columns:
occurred on a particular day, no error log will be created. The file is organized in a comma-
delimited format with 2 columns:
•
Time
. The time the error occurred.
•
Description
. The error description. One possible value can be max_ports, indicating the caller
was put on hold because all the Unified CVP license ports were taken. While the call was
eventually handled correctly, this is placed here as a notice that the license may not have
enough Unified CVP ports to match caller volume. Another value is bad_url:[URL],
indicating that a request was made to VXML Server for a URL that could not be recognized.
This most likely will occur if the voice browser refers to an application that does not exist.
The last description is error, indicating that some other error occurred.
eventually handled correctly, this is placed here as a notice that the license may not have
enough Unified CVP ports to match caller volume. Another value is bad_url:[URL],
indicating that a request was made to VXML Server for a URL that could not be recognized.
This most likely will occur if the voice browser refers to an application that does not exist.
The last description is error, indicating that some other error occurred.
Note that the global error log is not designed to be parsed, even though the columns are separated
with commas. This is because when the error log reports a Java-related error, it may include what
is called a “Java stack trace”, which contains multiple lines of output.
with commas. This is because when the error log reports a Java-related error, it may include what
is called a “Java stack trace”, which contains multiple lines of output.
The Global Error Logger utilizes a configuration to control how it logs certain types of errors and
how often the log files should be purged. The configuration is specified as an XML file created
by the designer and placed in the
how often the log files should be purged. The configuration is specified as an XML file created
by the designer and placed in the
conf
directory of Audium Home.