Audium Knowledge Base

Article ID:	308
Last updated:	January 19, 2007

Would you like to...

Print this page

Post a comment

User Opinions

No users have voted.

How would you rate this answer?

Helpful

Not helpful

This article describes a known issue in Audium Call Services 3.6.2 - 3.6.4, and a workaround to avoid it. Note that this issue has been resolved and will be included in the next post-3.6.4 maintenance release.

The Call Services global error log starts to grow rapidly, and server performance is significantly hindered. This is triggered by an error occurring while attempting to log an error. Inspecting the error log reveals a pattern of exceptions similar to the following:

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 that the text after "The error was:" in these examples may be different in your environment and circumstances. The key phrase to look for is "An error occurred while trying to log a different error encountered while attempting to log an event."

This issue has been resolved internally, and will be included in the next (post-3.6.4) maintenance release of Audium Call Services. In the interim, we recommend that you apply the following workaround to each deployed voice application:

Edit the file data/application/ActivityLogConfig.xml and remove (or comment out) the following lines:

<event id="systemError"/>
<event id="javaApiError"/>

Our testing indicates that it is these two events that have the potential to trigger this scenario, and so by preventing the ActivityLogger from listening to them, the situation can be avoided.