Hi all,
I reported a while back that we getting an exception related to the locks
(Oracle TIMESTAMP issue) table:
ang.ClassCastException: oracle.sql.TIMESTAMP cannot be cast to
java.sql.Timestamp
at org.springframework.scheduling.quar
Marv kindly shared his DDL with me for creating this table that fixes this
issue.
So here is the confusion. I have a test CAS server that uses the same incorrect
DDL for the locks table as our production server. It doesn't get this
exception! Both test and production consist of 2 CAS servers behind a reverse
proxy load balancer / same Oracle versions / etc.
I don't want to fix production until I can reproduce the error in test and then
prove the fix works. Could this be a load related issue and we are just luck
not to see it test?
Any ideas?
Thanks,
Bryan
--
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
