You must be logged in to perform this action
That message tell that the HTTP Session has been timed out (session time out destroys any active conversation).
How long are your http session defined?
yes you are right, so the Session timeout overrides the conversation timeout
I've got a problem with conversation-timeout too :
I set :
<core:manager concurrent-request-timeout="500" conversation-timeout="60" conversation-id-parameter="cid" conversation-is-long-running-parameter="clr"/>
in components.xml (I set the time-out very low for the test)
But I can't get a timeout message. If I'm right, the timeout is in milliseconds. I wait a lot more than 60 ms (1or 2 minutes) without being stopped by any message.
The only way for me to get the timeout message is to go further the session time-out (I tried to set it to 1 minute in the web.xml file and then I got the message of session time-out)
Do you know why the conversation-timeout is ignored? Has anyone got the same problem?
I'm using seam 1.2.1
I have the same low <core:manager> timeout setting and the same Seam version as "idylle" (the previous author).
My conversations simply don't timeout even with a timeout of 1 millisecond (my session timeout is 30 minutes).
Could anyone tell me how I can control my conversation timeouts??
<core:manager conversation-timeout="1" concurrent-request-timeout="500" conversation-id-parameter="cid" conversation-is-long-running-parameter="clr"/>
Conversations simply don't timeout...
The foreground conversation never times out. If you continue clicking inside that conversation, and your click submits a conversation identifier, that conversation is in the foreground and it will not timeout.