Yep, It looks like my DBAs got the DDL wrong. I did a desc on the locks table and it is a TIMESTAMP and not DATE.
Thanks! -Bryan -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Tuesday, January 10, 2012 7:58 AM To: [email protected] Subject: Re: [cas-user] CAS slow today > nested exception is java.lang.ClassCastException: oracle.sql.TIMESTAMP > cannot be cast to java.sql.Timestamp Pretty sure your LOCKS table has at least one wrong field datatype for JdbcLockingStrategy. Here's the DDL we used when we ran on Oracle (10g?): CREATE TABLE LOCKS ( APPLICATION_ID VARCHAR2(50) NOT NULL, UNIQUE_ID VARCHAR2(50) NULL, /** Must use DATE instead of TIMESTAMP on Oracle to prevent ClassCastException as discussed in SPR-4886 */ EXPIRATION_DATE DATE NULL ); ALTER TABLE LOCKS ADD CONSTRAINT LOCKS_PK PRIMARY KEY (APPLICATION_ID) ENABLE; I would imagine your EXPIRATION_DATE is a TIMESTAMP column instead of DATE as required on Oracle. 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
