• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Won't Fix
  • SpringRuntime
  • tgautier
  • Reporter: hhuynh
  • August 02, 2007
  • 0
  • Watchers: 1
  • July 27, 2012
  • October 29, 2007

Description

Exceptions:

org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.webflow.execution.repository.NoSuchFlowExecutionException: No flow execution could be found with key ‘_c391ACCC0-371D-1626-EF54-9D8894BFFA7F_k7076922B-06E0-41BF-CAE8-F6A7CDE709C6’ – perhaps this executing flow has ended or expired? This could happen if your users are relying on browser history (typically via the back button) that references ended flows.; nested exception is org.springframework.webflow.conversation.NoSuchConversationException: No conversation could be found with id ‘391ACCC0-371D-1626-EF54-9D8894BFFA7F’ – perhaps this conversation has ended? org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:487) org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:430) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

root cause

org.springframework.webflow.execution.repository.NoSuchFlowExecutionException: No flow execution could be found with key ‘_c391ACCC0-371D-1626-EF54-9D8894BFFA7F_k7076922B-06E0-41BF-CAE8-F6A7CDE709C6’ – perhaps this executing flow has ended or expired? This could happen if your users are relying on browser history (typically via the back button) that references ended flows.; nested exception is org.springframework.webflow.conversation.NoSuchConversationException: No conversation could be found with id ‘391ACCC0-371D-1626-EF54-9D8894BFFA7F’ – perhaps this conversation has ended? org.springframework.webflow.execution.repository.support.AbstractConversationFlowExecutionRepository.getConversation(AbstractConversationFlowExecutionRepository.java:242) org.springframework.webflow.execution.repository.support.AbstractConversationFlowExecutionRepository.getLock(AbstractConversationFlowExecutionRepository.java:121) org.springframework.webflow.executor.FlowExecutorImpl.refresh(FlowExecutorImpl.java:275) org.springframework.webflow.executor.support.FlowRequestHandler.handleFlowRequest(FlowRequestHandler.java:122) org.springframework.webflow.executor.mvc.FlowController.handleRequestInternal(FlowController.java:172) org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:857) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:792) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:475) org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:430) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

root cause

org.springframework.webflow.conversation.NoSuchConversationException: No conversation could be found with id ‘391ACCC0-371D-1626-EF54-9D8894BFFA7F’ – perhaps this conversation has ended? org.springframework.webflow.conversation.impl.ConversationContainer.getConversation(ConversationContainer.java:114) org.springframework.webflow.conversation.impl.SessionBindingConversationManager.getConversation(SessionBindingConversationManager.java:122) org.springframework.webflow.execution.repository.support.AbstractConversationFlowExecutionRepository.getConversation(AbstractConversationFlowExecutionRepository.java:239) org.springframework.webflow.execution.repository.support.AbstractConversationFlowExecutionRepository.getLock(AbstractConversationFlowExecutionRepository.java:121) org.springframework.webflow.executor.FlowExecutorImpl.refresh(FlowExecutorImpl.java:275) org.springframework.webflow.executor.support.FlowRequestHandler.handleFlowRequest(FlowRequestHandler.java:122) org.springframework.webflow.executor.mvc.FlowController.handleRequestInternal(FlowController.java:172) org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:857) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:792) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:475) org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:430) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

Comments

Hung Huynh 2007-08-03

I saw the same exception with WebFlowTest in our repo running with spring-webflow-1.0.4.jar but not with spring-webflow-1.0.jar

Fiona OShea 2007-08-06

Can you look into the error and get an understanding of the issue? thanks

Eugene Kuleshov 2007-08-15

Apparently this is a “feature” introduced in the Spring Web Flow 1.0.4. See http://opensource.atlassian.com/projects/spring/browse/SWF-304

That issue seem to be fixed today and probably will go into the next builds. See http://opensource.atlassian.com/projects/spring/browse/SWF-378

Now we can either explicitly workaround 1.0.4 code, or simply state that we support 1.0.3, anything after 1.0.4, but not the 1.0.4. Thoughts?

Eugene Kuleshov 2007-08-15

It took me some time to figure that out, but the reason it stopped working is that they randomized some keys in the clustered structures and in result we lost cluster-wide identity for those structures. More specifically sessionKey held by SessionBindingConversationManager

Kalai Kannaiyan 2007-08-15

I have seen this issue before with Version 2.2.1. please refer to LKC-3280

Fiona OShea 2007-10-29

issue resolved in webflow1.5