[OWB-370] Intransient Conversation context get rdestroyed randomly by destroyWithRespectToTimout

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: M4
• Fix Version/s: 1.0.0-alpha-1
• Component/s: Context and Scopes
• Assignee: Ying Wang
• Reporter: Ying Wang
• Created: 12/May/10 23:44
• Updated: 12/May/10 23:59
• Resolved: 12/May/10 23:59

Description

Before we put conversation context into ConversationManager's hashmap, we should update the conversation's activeTime once. Else with 0 activeTime, the conversation might be destroyed by timeout before we could update it in afterPhase step.