[LIKELY_SPAM]Re: login screen timeout

[Scott Battaglia]

Thanks, something must have happened to the mechanism that maps that error
to the resolver.  If anyone can open a JIRA issue with the stack trace, etc.
that would be great and then I can take a look.

-Scott

-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia


On Thu, Aug 28, 2008 at 1:25 PM, Wyles, Eric <EWyles at uams.edu> wrote:

>  FYI, I have seen this error as well and I have not disabled any exception
> catching.
>
>
>  ------------------------------
>
> *From:* cas-bounces at tp.its.yale.edu [mailto:cas-bounces at tp.its.yale.edu] *On
> Behalf Of *Scott Battaglia
> *Sent:* Thursday, August 28, 2008 11:47 AM
> *To:* Yale CAS mailing list
> *Subject:* [LIKELY_SPAM]Re: login screen timeout
>
>
>
> We actually have a thing that's supposed to catch that exception and
> redisplay the login page.  Assuming you haven't disabled that, this would be
> a bug.  If you haven't disabled it can you open up a JIRA issue for it and
> we'll take a look at it.
>
> Thanks
> -Scott
>
> -Scott Battaglia
> PGP Public Key Id: 0x383733AA
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>
>  On Thu, Aug 28, 2008 at 12:38 PM, K S <kevsout at gmail.com> wrote:
>
> Hi,
>
>
>
> Our users get the following HTTP Status 500 error displayed on their
> browser when taking too long typing their credentials to our cas-server v3.3
> (not sure of the delay, but it's long), and was wondering what is generally
> done to present something prettier or return to the login page.
>
>
>
> Thanks,
>
> Kev
>
>
>
>
>
> type Exception report
>
>
>
> message
>
>
>
> description The server encountered an internal error () that prevented it
> from fulfilling this request.
>
>
>
> exception
>
>
>
> org.springframework.webflow.execution.repository.NoSuchFlowExecutionException:
> No flow execution could be found with key
> '_cF530762C-B915-4842-B108-80EE720D13F3_kE0734066-5050-8291-26CD-34EF58D3159F'
> -- 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 'F530762C-B915-4842-B108-80EE720D13F3'
> -- perhaps this conversation has ended?
>
>
> org.springframework.webflow.execution.repository.support.AbstractConversationFlowExecutionRepository.getConversation(AbstractConversationFlowExecutionRepository.java:229)
>
>
> org.springframework.webflow.execution.repository.support.AbstractConversationFlowExecutionRepository.getLock(AbstractConversationFlowExecutionRepository.java:119)
>
>
> org.springframework.webflow.executor.FlowExecutorImpl.resume(FlowExecutorImpl.java:217)
>
>
> org.springframework.webflow.executor.support.FlowRequestHandler.handleFlowRequest(FlowRequestHandler.java:111)
>
>
> org.springframework.webflow.executor.mvc.FlowController.handleRequestInternal(FlowController.java:165)
>
>
> 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:875)
>
>
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
>
>
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
>
>
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511)
>
>             javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
>
>             javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>
>
> org.jasig.cas.web.init.SafeDispatcherServlet.service(SafeDispatcherServlet.java:115)
>
>
> org.inspektr.common.web.ClientInfoThreadLocalFilter.doFilterInternal(ClientInfoThreadLocalFilter.java:48)
>
>
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
>
>
>
>
>
> note The full stack trace of the root cause is available in the Apache
> Tomcat/5.5.26 logs.
>
>
>
>
>
>
>
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
>
> Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
>
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20080828/5697e59d/attachment.html