I don't think that's the issue in my case. I have seen this error when
the login page has been up for less than 15 seconds so I highly doubt
that a login timout would have been hit in that short of a time frame.
I will look into this route more, though. Thanks.
On 01/09/2012 03:55 PM, Jon Gorrono wrote:
Not mentioned so far: it looks like it might be a session timeout on
the login screen per this (human) conversation in this forum last
Summer:
http://comments.gmane.org/gmane.comp.java.jasig.cas.user/17973
... which references https://issues.jasig.org/browse/CAS-992
On Mon, Jan 9, 2012 at 2:34 PM, Jared Hoover<[email protected]> wrote:
Here's the error I'm getting:
Jan 9, 2012 11:10:21 AM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet cas threw exception
org.springframework.webflow.conversation.NoSuchConversationException: No
conversation could be found with id '1' -- perhaps this conversation has
ended?
at
org.springframework.webflow.conversation.impl.ConversationContainer.getConversation(ConversationContainer.java:134)
at
org.springframework.webflow.conversation.impl.SessionBindingConversationManager.getConversation(SessionBindingConversationManager.java:116)
at
org.springframework.webflow.execution.repository.support.AbstractFlowExecutionRepository.getConversation(AbstractFlowExecutionRepository.java:183)
at
org.jasig.cas.web.flow.CasFlowExecutionKeyFactory.validateUUID(CasFlowExecutionKeyFactory.java:138)
at
org.jasig.cas.web.flow.CasFlowExecutionKeyFactory.parseFlowExecutionKey(CasFlowExecutionKeyFactory.java:102)
at
org.springframework.webflow.executor.FlowExecutorImpl.resumeExecution(FlowExecutorImpl.java:164)
at
org.springframework.webflow.mvc.servlet.FlowHandlerAdapter.handle(FlowHandlerAdapter.java:183)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:790)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:719)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:644)
at
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:560)
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_aroundBody2(SafeDispatcherServlet.java:115)
at
org.jasig.cas.web.init.SafeDispatcherServlet.service_aroundBody3$advice(SafeDispatcherServlet.java:44)
at
org.jasig.cas.web.init.SafeDispatcherServlet.service(SafeDispatcherServlet.java:1)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
com.github.inspektr.common.web.ClientInfoThreadLocalFilter.doFilter(ClientInfoThreadLocalFilter.java:63)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
at
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
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:127)
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:298)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:662)
It looks like it's always the same error message but sometimes the id is a
different single digit number and most often it's 1. I also have changed us
from java 1.7.0 back to java 1.6.0_27 on this server.
Thanks,
Jared
On 09/27/2011 11:55 AM, Tillinghast, Andrew P. wrote:
CAS unavailable is the default error handling for any error encountered by
CAS.
If you have a development instance of CAS you can comment out
the<error-page> entries in your web.xml and the errors will display
onscreen.
Depending on the the nature of the error, particularly jsp errors, the
error will log to you localhost log file instead of the CAS or Catalina log
files. i.e. localhost.2011-09-27.log
-Andrew
On Sep 27, 2011, at 2:43 PM, Jared Hoover wrote:
We have a CAS 3.4.8 server configured for ldap against our AD
infrastructure. It allows SSO to our various web applications and to google
apps. On occasion when a user has entered their username/password at the
CAS login screen they're presented with an error message saying that "CAS is
unavailable". I've searched around and haven't found anything conclusive on
this error message. I'm not seeing any errors in the catalina.out log file
either. It's running on Tomcat 6.0.24 with jdk 1.7.0 x86_64. Any
assistance in resolving this would be greatly appreciated.
Thanks,
Jared
--
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
