I figured that out -- needed        

xmlns:util="http://www.springframework.org/schema/util"; 
and       
xsi:schemaLocation="http://www.springframework.org/schema/beans 
http://www.springframework.org/schema/beans/spring-beans-3.1.xsd
                                
http://:util="http://www.springframework.org/schema/util";
                                w.springframework.org/schema/util  
http://www.springframework.org/schema/util/spring-util-3.1.xsd";>
added to the <beans> declaration.

However, I'm still seeing some strange memcached things.

To wit:

If memcached is not running at all, I can still log in.  

Any idea what the hell's going on?

- Aaron 

> -----Original Message-----
> From: Aaron Bennett [mailto:[email protected]]
> Sent: Monday, August 12, 2013 11:40 AM
> To: [email protected]
> Subject: [cas-user] memcache ticket registry error
> 
> Hi,
> 
> Using Tomcat 7.0.42, maven 3.1.0, and cas 3.5.2, I get this error in cas.log
> when I try to enable the memcached ticket registry:
> 
> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 52 in XML document from ServletContext resource [/WEB-INF/spring-
> configuration/ticketRegistry.xml] is invalid; nested exception is
> org.xml.sax.SAXParseException; lineNumber: 52; columnNumber: 104; The
> prefix "util" for element "util:constant" is not bound.
> 
> Here's the relevant snippet from ticketRegistry.xml:
> <bean id="memcachedClient"
> class="net.spy.memcached.spring.MemcachedClientFactoryBean"
>        p:servers="${memcached.servers}"
>        p:protocol="${memcached.protocol}"
>        p:locatorType="${memcached.locatorType}"
>        p:failureMode="${memcached.failureMode}"
>        p:transcoder-ref="kryoTranscoder">
>    <property name="hashAlg">
>      <util:constant static-
> field="net.spy.memcached.DefaultHashAlgorithm.${memcached.hashAlgorit
> hm}" />
>    </property>
> </bean>
> 
> If I comment out the <property name="hashAlg"> </property> clause, then
> it builds and seems to work, except that even though I have two nodes with
> the same config, they don't seem to be able to share tickets.
> 
> Thanks for looking, everyone--
> 
> Aaron
> 
> ---
> Aaron Bennett
> Manager of Systems Administration
> Clark University ITS
> W:508.793.7315
> 
> 
> --
> 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