[SHIRO-164] The request/response pair should be available at all times to web-related components

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: Session Management
• Assignee: Les Hazlewood
• Reporter: Tauren Mills
• Created: 18/May/10 03:10
• Updated: 11/Jun/10 22:01
• Resolved: 19/May/10 16:42

Description

According to Les, for web-initiated interaction, you should not be seeing these messages:

DEBUG - DefaultWebSessionManager - No request or response bound to
the thread. Session ID cookie cannot be removed. This could occur in
a web application that also services non web clients (e.g. RMI
remoting).
DEBUG - DefaultWebSessionManager - Request or response object is not
bound to the thread. Assuming this session start activity is due to a
non web request (possible in a web application that also services non
web clients.

Full thread available here, with logs:
http://shiro-user.582556.n2.nabble.com/Intermittent-problems-with-SecurityUtils-getSubject-getPrincipal-td5067869.html#a5068081