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??
View
My setting:
core:manager conversation-timeout=1
| concurrent-request-timeout=500
| conversation-id-parameter=cid
| conversation-is-long-running-parameter=clr/
Conversations simply don't timeout...
View the original post :
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.
View the original post :
Thanks Christian, I have found this topic that gives some more insights:
http://www.jboss.com/index.html?module=bbop=viewtopicp=3970409
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4079751#4079751
Reply to the post :
Hi,
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
Thanks Fernando
yes you are right, so the Session timeout overrides the conversation timeout
thanks again
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4047779#4047779
Reply to the post :
anonymous wrote :
| 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?
View the original post :
