NoSuchFlowExecutionException

[Dan McLaughlin]

This is on IDP 5.0.   I've narrowed it down to something in the
IdentifierGenerationStrategy rework.  If I figure out what in the
change is breaking things, I'll open a ticket since the related ticket
has been resolved.

--

Thanks,

Dan

On Wed, Oct 19, 2022 at 6:23 PM Nate Klingenstein <ndk at signet.id> wrote:
>
> Dan,
>
> This is a fairly common error and a more appropriate question for the users' list.  In its most literal sense, it just means that the IdP [node] has no flow conversation in memory that corresponds to the e2s1 state presented by the client.
>
> You'll need to supply us with more details of the deployment and the usage pattern that leads to the exception.  It can be anything from bad clustering to JSESSIONID cookie mishandling and everything in between.
>
> Sorry to not have anything definitive,
> Nate
>
> --------
> Signet, Inc.
> The Art of Access ®
>
> https://www.signet.id
>
> -----Original message-----
> From: Dan McLaughlin via dev
> Sent: Wednesday, October 19 2022, 5:10 pm
> To: Shib Dev
> Cc: Dan McLaughlin
> Subject: NoSuchFlowExecutionException
>
> Any pointers on where I would look for what might be causing this exception?
>
> 2022-10-19 17:56:32,728 - 12.116.187.226 - DEBUG
> [org.springframework.webflow.executor.FlowExecutorImpl:160] - Resuming
> flow execution with key 'e2s1
> 2022-10-19 17:56:32,729 - 12.116.187.226 - ERROR
> [org.springframework.webflow.execution.repository.NoSuchFlowExecutionException:91]
> -
> org.springframework.webflow.execution.repository.NoSuchFlowExecutionException:
> No flow execution could be found with key 'e2s1' -- 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.
> at org.springframework.webflow.execution.repository.support.AbstractFlowExecutionRepository.getConversation(AbstractFlowExecutionRepository.java:172)
> Caused by: org.springframework.webflow.conversation.NoSuchConversationException:
> No conversation could be found with id '2' -- perhaps this
> conversation has ended?
> at org.springframework.webflow.conversation.impl.ConversationContainer.getConversation(ConversationContainer.java:124)
> 2022-10-19 17:56:32,729 - 12.116.187.226 - DEBUG
> [org.springframework.web.servlet.DispatcherServlet:1362] - Using
> resolved error view: ModelAndView [view="error";
> model={exception=org.springframework.webflow.execution.repository.NoSuchFlowExecutionException:
> No flow execution could be found with key 'e2s1' -- 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.,
> request=org.apache.catalina.connector.RequestFacade at 1070fdac,
> encoder=class net.shibboleth.shared.codec.HTMLEncoder,
> springContext=Root WebApplicationContext, started on Wed Oct 19
> 17:39:57 CDT 2022,
> response=net.shibboleth.shared.spring.servlet.impl.DynamicResponseHeaderFilter$ResponseProxy at 1fe54716}]
> 2022-10-19 17:56:32,730 - 12.116.187.226 - DEBUG
> [org.springframework.web.servlet.DispatcherServlet:1128] - Completed
> 500 INTERNAL_SERVER_ERROR
>
> --
>
> Thanks,
>
> Dan
> --
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net <mailto:dev-unsubscribe at shibboleth.net>
>
>