When you say you abandon the conversation what do you mean? Do you start a new conversation and begin interacting with it? The reason I ask is because the foreground conversation never times out. Background conversations will timeout according to your configured conversation-timeout. Background conversations are simply inactive conversations (conversations that the user is not currently interacting with). The foreground conversation is the last conversation the user interacted with. Hope that helps.
Sorry, should have previewed. When I say the foreground conversation never times out, I mean that it is tied to the session timeout not the configured conversation-timeout.
User logs in and is presented with a menu page. They click a menu option, starting a conversation that lasts for three pages. If they get up and walk away after getting to page 2, shouldn't the new conversation time out after 2 minutes? They would still be logged in, but the conversation should be dead. Or have I misunderstood something?
No, in this case that would be the foreground conversation which means that it would only timeout if the session timed out. Now, if the user was to navigate elsewhere and a different conversation was started, the previous conversation would then become a background conversation. In that case, the background conversation would timeout after 2 minutes. I hope that helps to clarify the scenario.
Yes, thank you!
Did Seam always work this way? If not, what version started to behave in this manner.
I was under the same assumption as whafrog.
From my understanding it has always worked this way. Here is a JIRA issue that requests documentation of the subject and references some earlier postings (all the way back to 1.0.1GA):
I wrote a blog posting last night that describes the conversation-timeout in-depth as I have seen a lot of postings asking about this:
Hope it helps.