What does an Application Fault containing "Aquarium|screenLoop" mean? Cisco Content Security Appliances

Introduction

This document describes typical root cause of error "Aquarium|screenLoop" seen.

Background Information

Single instances of these Application Faults can be regarded as benign. They are typically caused by submitting the same web page twice in rapid succession. Frequent or periodic Application Faults deserve further investigation by Customer Support.

Some examples of these include: 

An application fault occurred: (('CoroSessionContainer', '__getitem__',
'230'), 'aquarium.session.CoroSessionContainer.CoroSessionKeyError',
'<exceptions.KeyError instance at 0x995684c>',
'[Aquarium|screenLoop|344] [InternalLibrary|inverseExtend|321]
[InternalLibrary|__call__|735] [Bare|__call__|579]
[InternalLibrary|__call__|735] [CssAndJavaScript|__call__|452]
[InternalLibrary|__call__|735] [Sparse|__call__|977]
[NameMapper|valueFromSearchList|250] [NameMapper|_valueForName|229]
[Complete|doPrimaryNavigation|134] [InternalLibrary|call|273]
[PrimaryComplete|__call__|105] [NameMapper|valueForName|212]
[NameMapper|_valueForName|229] [Map|getFilteredMap|203]
[Map|_getFilteredMap|220] [Map|hasAccess|271]
[CoroSessionContainer|__getitem__|230]')

An application fault occurred: (('scheduled_reports_super',
'doSaveNewAction', '200'), 'exceptions.KeyError', "'name'",
'[Aquarium|screenLoop|397] [InternalLibrary|inverseExtend|321]
[InternalLibrary|__call__|739] [Controller|__call__|23]
[InternalLibrary|__call__|739] [CommonController|__call__|38]
[InternalLibrary|__call__|739] [AppController|__call__|127]
[InternalLibrary|__call__|741] [scheduled_reports_new|__call__|29]
[scheduled_reports_super|executeAction|172]
[Controller|executeAction|65]
[scheduled_reports_super|doSaveNewAction|200]')