-
1. Re: conversation timeout
gavin.king Jul 31, 2006 12:53 PM (in response to nepoez79)Conversation timeouts occur during requests. If you aren't making any requests to the server, they won't timeout.
Put a breakpoint in org.jboss.seam.core.Manager.conversationTimeout(ExternalContext externalContext) to see it happen. -
2. Re: conversation timeout
kasim Oct 26, 2006 1:56 PM (in response to nepoez79)
Oh. So you can make it so your invididual request are in a time based manner. So if i want to make sure my server responds in 10 seconds regardless?
at least thats what i am gathering from this part of the doco
"Allows the conversation timeout to be set per-conversation, and the conversation description and switchable outcome to be set when the application requires workspace management functionality."
? -
3. Re: conversation timeout
cja987 Oct 26, 2006 3:34 PM (in response to nepoez79)The conversation timeout controls how quickly open conversations expire -- it's the direct equivalent of session timeouts, but for conversations. It has nothing to do with server timeouts, which are specific to the webserver. I imagine for JBoss, it would be somewhere in the tomcat configuration.
-
4. Re: conversation timeout
kasim Oct 26, 2006 6:48 PM (in response to nepoez79)"cja987" wrote:
The conversation timeout controls how quickly open conversations expire -- it's the direct equivalent of session timeouts, but for conversations. It has nothing to do with server timeouts, which are specific to the webserver. I imagine for JBoss, it would be somewhere in the tomcat configuration.
Ahhh i didnt think i'd be that lucky.
No i was just thinking back to the last project i was on. The users could make requests to us and set a time out. So we had to launch thinks in threads.