I'm not sure how much help I can be unless we can isolate what's causing it.

Scott

On Wed, Sep 30, 2009 at 10:00 AM, Jean-Noël Colin <[email protected]>wrote:

> It has been reported with recent browsers, i.e. IE8 or FF3.5. There's no
> caching. The only thing that makes our setup a bit special is that Tomcat
> https port is 6443, and since this port (as other non-standard ports) is
> blocked by some school proxies, we are using iptables to reroute packets
> from port 443 to port 6443. If you think this might have an influence, I can
> try to setup tomcat to use port 443 (we don't like that since it means
> tomcat has to run as root)
> Jean-Noel
>
> On 30 Sep 2009, at 14:45, Scott Battaglia wrote:
>
> Is it in any particular browsers?  Is there any caching that goes on in
> between?
>
> We've been running for years and rarely see this error (and its generally
> because someone waited until their session timed out to submit the login
> page).
>
>
> On Wed, Sep 30, 2009 at 12:14 AM, Jean-Noël Colin <[email protected]>wrote:
>
>> Scott,
>> We made no change in the CAS timeout configuration.
>> In tomcat/cont  web.xml, session timeout is set to 30 minutes
>> In webapps/cas/WEB-INF/web.xml, session timeout is set to 5 minutes
>> In ticketExpirationPolicies.xml , service ticket expiration is set to 5
>> minutes (300000msec) while the granting ticket expiration is set to 2h
>> (7200000msec)
>>
>> Jean-Noël
>>
>>
>> On 30 Sep 2009, at 04:39, Scott Battaglia wrote:
>>
>> Have you changed any CAS configuration?  Typically the only time the flow
>> can't be found is if a session times out.
>>
>>
>> On Tue, Sep 29, 2009 at 10:34 AM, Jean-Noël Colin <[email protected]>wrote:
>>
>>> Hi
>>>
>>> We are running CAS 3.3.2 on Tomcat 6.0.18; we have two client services: a
>>> site built in ColdFusion and a Liferay Portal.
>>>
>>> We have a recurring problem that makes CAS unusable for some users. After
>>> logging in with CAS and visiting a service, and then logging out from the
>>> service after a while, when returning to CAS login screen, users can't login
>>> anymore, and CAS loops on the login form. In the logs, we find an exception
>>> like the one shown below.
>>>
>>> I checked, and it's not linked to user pressing the back button, nor to
>>> user crafting POST request. It's really annoying, because a) it's not
>>> reproduceable, and b) it is blocking users.
>>>
>>> Any help would be appreciated to solve this issue.
>>>
>>> Best regards
>>>
>>> Jean-Noel Colin
>>>
>>> 2009-09-29 16:17:39,794 DEBUG
>>> [org.jasig.cas.web.NoSuchFlowExecutionExceptionResolver] - <Error getting
>>> flow information for URL:/cas/login?service=
>>> http://www.etwinning.net/tools/CASRedirectToPortalAfterAuthentication.cfm
>>> >
>>> org.springframework.webflow.execution.repository.NoSuchFlowExecutionException:
>>> No flow execution could be found with key
>>> '_c3ADF2F78-0943-9BBF-E94E-00D9B7511ED4_kE32ACF27-8ACB-5B0C-B0E5-DE9719175AC8'
>>> -- 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 '3ADF2F78-0943-9BBF-E94E-00D9B7511ED4'
>>> -- perhaps this conversation has ended?
>>>        at
>>> org.springframework.webflow.execution.repository.support.AbstractConversationFlowExecutionRepository.getConversation(AbstractConversationFlowExecutionRepository.java:229)
>>>        at
>>> org.springframework.webflow.execution.repository.support.AbstractConversationFlowExecutionRepository.getLock(AbstractConversationFlowExecutionRepository.java:119)
>>>        at
>>> org.springframework.webflow.executor.FlowExecutorImpl.resume(FlowExecutorImpl.java:217)
>>>        at
>>> org.springframework.webflow.executor.support.FlowRequestHandler.handleFlowRequest(FlowRequestHandler.java:111)
>>>        at
>>> org.springframework.webflow.executor.mvc.FlowController.handleRequestInternal(FlowController.java:165)
>>>        at
>>> org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
>>>        at
>>> org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
>>>        at
>>> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
>>>        at
>>> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:807)
>>>        at
>>> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
>>>        at
>>> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511)
>>>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
>>>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>>>        at
>>> org.jasig.cas.web.init.SafeDispatcherServlet.service(SafeDispatcherServlet.java:115)
>>>        at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>>>        at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>>        at
>>> org.inspektr.common.web.ClientInfoThreadLocalFilter.doFilterInternal(ClientInfoThreadLocalFilter.java:48)
>>>        at
>>> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
>>>        at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>>>        at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>>        at
>>> org.eun.authentication.cas.filter.CharsetFilter.doFilter(CharsetFilter.java:30)
>>>        at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>>>        at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>>        at
>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>>>        at
>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>>>        at
>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>>>        at
>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>>>        at
>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>>>        at
>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
>>>        at
>>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
>>>        at
>>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
>>>        at
>>> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>>>        at java.lang.Thread.run(Thread.java:619)
>>>
>>> --
>>> 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
>>>
>>
>> --
>> 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
>>
>>
>>  --
>> 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
>>
>>
> --
> 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
>
>
> --
> 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
>
>

-- 
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

Reply via email to