> Have you suggestions to avoid this problem? There is only one solution at present. Enable session affinity in your load balancer so the user is always directed to the same node containing servlet session-based flow state. Session affinity alone does not account for moving the user to another node due to node loss or other causes. I would argue those are edge cases that are acceptable for the short intervals needed to maintain the login webflow, which is typically measured in seconds. If you must support the edge case, clustering session storage should provide a solution. Personally I don't believe it's worth the effort.
I should note that the 1.0 version of Spring Webflow provided a flow state management strategy, http://static.springsource.org/spring-webflow/docs/1.0.x/api/org/springframework/webflow/execution/repository/continuation/ClientContinuationFlowExecutionRepository.html, that required no server-side state. Unfortunately it was removed in 2.x, which we are using at present. It's my understanding support for this feature in some form or another will be restored in Webflow 3.x, but I can find no reference to it. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
