[ORCHESTRA-14] ConversationManagerSessionListener leak & IllegalStateException

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1
• Fix Version/s: 1.1
• Component/s: Conversation
• Environment: tomcat 5
• Assignee: Thomas Spiegl
• Reporter: Thomas Spiegl
• Created: 08/Jan/08 16:00
• Updated: 11/Jan/08 08:10
• Resolved: 08/Jan/08 16:21

Description

ConversationManagerSessionListener has serveral issues:

1) attributeReplaced sets the old instance of conversationManager in conversationWiperThread instead of the new one
2) on session expire ConversationManagerSessionListener.attributeRemoved is getting called and session.getId() throws IllegalStateException
3) ConversationManagerSessionListener.sessionDestroyed will throw a IllegalStateException as well -> method is useless

Solution:
1) use a unique id for conversationManager instead of session.getId() as a key in conversationWiperThread
2) remove HttpSessionListener interface from ConversationManagerSessionListener