Cache timeout calculation has a hole in the event no Sessions properties are found

Description

The function returning the app-specific cache timeout to use is coded to assume app.getPropertySet("Sessions") will always succeed. I think that's true, but it isn't safe.

Environment

None

Activity

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Created December 17, 2010 at 2:22 PM
Updated January 31, 2011 at 9:10 PM
Resolved December 17, 2010 at 2:33 PM