Access logs
There are two sets of access logs, the webserver logs
(IIS/Apache) and the platform access logs (JBoss/Weblogic). Together, both logs can be used to tracing
command calls through the eGain system in order to identify connection issues
or slow response times. These can be
found in the following locations:
IIS
\inetpub\logs\LogFiles
Apache
To
find exact apache log file location, use the appropriate grep command on your
httpd.conf:
# grep ErrorLog
/usr/local/etc/apache22/httpd.conf
# grep ErrorLog /etc/apache2/apache2.conf
# grep ErrorLog /etc/httpd/conf/httpd.conf
# grep ErrorLog /etc/apache2/apache2.conf
# grep ErrorLog /etc/httpd/conf/httpd.conf
JBoss
\jboss-as-7.1.2.Final-13.01.2014\standalone\log
Weblogic
Consult your oracle documentation
JVM logs
.hprof logs are generated if the JVM crashes and can be
found in the eGain log directory with the file extension .hprof
Java_pid<nnnn>.hprof
Use Eclipse and the Memory Analyser plugin to analyse hprof files
Use Eclipse and the Memory Analyser plugin to analyse hprof files
JBoss
Log files are created when there is an error in JBoss and
can be found in the eGain log directory with the following file name (where <nnnn>
is the process id):
Hs_err_pid<nnnn>.log
No comments:
Post a Comment