Houston I think we have a problem. In my log file I see this:
[#|2012-01-10T06:36:10.441-0700|INFO|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=215;_ThreadName
=Thread-2;|2012-01-10 06:36:10,441 INFO
[org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] -
<Beginning ticket cleanup.>
|#]
But a few lines later I see this exception:
[#|2012-01-10T06:36:10.462-0700|INFO|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=215;_ThreadName=Thread-2;|2012-01-10
06:36:10,460 ERROR [org.quartz.core.JobRunShell] - <Job
DEFAULT.ticketRegistryCleanerJobDetail threw an unhandled Exception: >
org.springframework.scheduling.quartz.JobMethodInvocationFailedException:
Invocation of method 'clean' on target class [class
org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] failed;
nested exception is java.lang.ClassCastException: oracle.sql.TIMESTAMP cannot
be cast to java.sql.Timestamp
at
org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:273)
at
org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)
Caused by: java.lang.ClassCastException: oracle.sql.TIMESTAMP cannot be cast to
java.sql.Timestamp
at
com.sun.rowset.CachedRowSetImpl.getTimestamp(CachedRowSetImpl.java:2262)
at
com.sun.rowset.CachedRowSetImpl.getTimestamp(CachedRowSetImpl.java:2713)
at
org.springframework.jdbc.support.rowset.ResultSetWrappingSqlRowSet.getTimestamp(ResultSetWrappingSqlRowSet.java:515)
at
org.jasig.cas.ticket.registry.support.JdbcLockingStrategy.canAcquire(JdbcLockingStrategy.java:330)
I think this explains why our ticket registry has 2 million rows. I'll take a
look at the source to see if I can fix this problem. Hopefully I just have a
config error that will fix this issue.
-Bryan
-----Original Message-----
From: Marvin Addison [mailto:[email protected]]
Sent: Tuesday, January 10, 2012 6:54 AM
To: [email protected]
Subject: Re: [cas-user] CAS slow today
> Ok following the link you sent I see that do have a ticketRegistery.xml file
> in my overlay build.
What you have looks reasonable. If you have wiring problems, I'd expect
deployment errors that I assume you're not having. So let's assume it's wired
correctly. You should do some careful log review to determine whether the
cleaner is running. It has very obvious log entries.
If it's not running, then I'd recommend you check to see whether you have a
Quartz scheduler driving periodicTicketRegistryCleanerTrigger.
Newer versions of CAS use
org.jasig.cas.util.AutowiringSchedulerFactoryBean to scan for triggers anywhere
in the Spring context and install them. In any case make sure you have
something that's driving the trigger.
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
