This document describes a known issue in Cisco Unified Call Services,
Universal Edition, and a workaround to avoid it. Note that this issue has been
resolved, is included in post-3.6.4 maintenance releases, and is relevant to
Version 3.6.4 and earlier.
There are no specific requirements for this document.
The information in this document is based on Cisco Unified Call
Services, Universal Edition, Version 3.6.4 and earlier.
Technical Tips Conventions for more information on document
Symptoms: The Call Services global error log starts to
grow rapidly, and server performance is significantly hindered. This is
triggered by an error that occurs while when an attempt is made to log an
error. Inspection of the error log reveals a pattern of exceptions similar to
01/08/2007 08:10:59, SERVER ERROR: An error occurred while trying to log a different error
encountered while attempting to log an event. A listing of the original error follows this one in the
error log. The error was: java.lang.IllegalStateException: getAttribute: Session already invalidated
01/08/2007 08:10:59, SERVER ERROR: An error was encountered while attempting to log an event with the ID
"javaApiError". The error was: java.lang.IllegalStateException: getAttribute: Session already invalidated
Note: The text after The error was: in these examples
can be different in your environment and circumstances. The key phrase to look
for is this: An error occurred while trying to log a different error
encountered while attempting to log an event.
Resolution: This issue has been resolved internally,
and will be included in the next post-3.6.4 maintenance release of Cisco
Unified Call Services. In the interim, apply this workaround to each deployed
Edit the file data/application/ActivityLogConfig.xml and remove (or
comment out) these lines:
Tests indicate that these two events have the potential to trigger
this scenario. If you do not allow the ActivityLogger to listen to them, the
situation can be avoided.