Glad you found the reason. Just a note that our filters support supplying values at the context-param level. So if two filters need the same value, instead of supplying it as an init param you can supply it at a higher level.
Cheers, Scott On Wed, Nov 11, 2009 at 11:29 AM, Hoi Chong <[email protected]> wrote: > Hi Scott, Marvin, > Thanks for the pointers. > > I did a more thorough check on other log files (localhost.2009-11-12.log) > and found this exception... > > Nov 12, 2009 12:14:07 AM org.apache.catalina.core.StandardContext > filterStart > SEVERE: Exception starting filter CAS Validation Filter > java.lang.IllegalArgumentException: serverName or service must be set. > at org.jasig.cas.client.util.CommonUtils.assertTrue(CommonUtils.java:88) > at > org.jasig.cas.client.util.AbstractCasFilter.init(AbstractCasFilter.java:84) > at > org.jasig.cas.client.validation.AbstractTicketValidationFilter.init(AbstractTicketValidationFilter.java:74) > > Turns out, it must have a parameter for serverName in the CAS Validation > Filter. > Added that in, and it is working fine now. > > > <filter> > <filter-name>CAS Validation Filter</filter-name> > > <filter-class>org.jasig.cas.client.validation.Cas20ProxyReceivingTicketValidationFilter</filter-class> > <init-param> > <param-name>casServerUrlPrefix</param-name> > <param-value>https://localpc/cas</param-value> > </init-param> > <init-param> > <param-name>serverName</param-name> > <param-value>http://localpc:9090</param-value> > </init-param> > </filter> > > Best Regards. > Hoi Chong > > > > > Marvin Addison wrote: > >> CAS server will start nicely, but examples webapp will fail to start with >>> the following error message >>> Nov 11, 2009 1:14:06 AM org.apache.catalina.core.StandardContext start >>> SEVERE: Error filterStart >>> Nov 11, 2009 1:14:06 AM org.apache.catalina.core.StandardContext start >>> SEVERE: Context [/examples] startup failed due to previous errors >>> >>> >> >> Typically the cause of a failed servlet start is logged previously, as >> indicated by the text of the last message above. The cause would >> likely have more specific information that could help us diagnose your >> problem. Can you provide the stack trace that precedes the message >> above? In some cases the message may not be written to the >> console.log file, which I believe is the one you have quoted above. >> The $TOMCAT_HOME/logs/catalina.out file may contain the information >> you want in that case. >> >> M >> >> >> > > > -- > 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
