Thanks, Marvin. We've got an Oracle11 database here, and our LOCKS table is
also missing, I think due to the same configuration issue here.
For the JdbcLockingStrategy bean, are you referring to the bean with
id="cleanerLock";
<bean id="cleanerLock"
class="org.jasig.cas.ticket.registry.support.JdbcLockingStrategy"
p:uniqueId="${host.name}"
p:platform="${ticket.cleaner.database.platform}"
p:applicationId="cas-ticket-registry-cleaner"
p:dataSource-ref="dataSource"
/>
If so, then when defining this property, ${ticket.cleaner.database.platform},
is there a short-list of known-values we should be specifying there ?
Thanks for your help with this question...
Corey S.
> -----Original Message-----
> From: Marvin Addison [mailto:[email protected]]
> Sent: September 1, 2010 10:10 AM
> To: [email protected]
> Subject: Re: [cas-user] MySQL Ticket Registry - table not created
>
> > The service registry tables are apparently created correctly, but the
> ticket registry is missing the locks table. Am I missing a property
> somewhere?
>
> Likely. You need to provide a valid uniqueId in the
> JdbcLockingStrategy bean. That bean is responsible for creating the
> dialect-specific lock table, which would not be possible if the bean
> can't be initialized. The host.name property is defined in
> cas.properties, although you could provide a static value. If you're
> certain cas.properties has host.name defined, please provide excerpts
> of your cas.log file that should contain errors on deployment.
>
> 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
