Sure. You're right, we are persisting into durable storage.
We have modified several parts of the app, but the error is happening
with the default Quartz section in ticketRegistry.xml. This is that
snippet:
<!--Quartz -->
<!-- TICKET REGISTRY CLEANER -->
<bean id="ticketRegistryCleaner"
class="org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleane
r"
p:ticketRegistry-ref="ticketRegistry" />
<bean id="jobDetailTicketRegistryCleaner"
class="org.springframework.scheduling.quartz.MethodInvokingJobDetailFact
oryBean"
p:targetObject-ref="ticketRegistryCleaner"
p:targetMethod="clean" />
<bean id="triggerJobDetailTicketRegistryCleaner"
class="org.springframework.scheduling.quartz.SimpleTriggerBean"
p:jobDetail-ref="jobDetailTicketRegistryCleaner"
p:startDelay="20000"
p:repeatInterval="5000000" />
<bean id="scheduler"
class="org.springframework.scheduling.quartz.SchedulerFactoryBean">
<property name="triggers">
<list>
<ref
local="triggerJobDetailTicketRegistryCleaner" />
</list>
</property>
</bean>
I've done some reading up on this and it seems that
MethodInvokingJobDetailFactoryBean is not serializable and therefore
cannot be used when Quartz is using a persisted store. What doesn't
make sense to me about this is that I feel like somebody must have come
across this by now using CAS if this were the case (and therefore would
have a workaround). This is why we attempted switching to the
JpaTicketRegistry to fix the problem, but it did not fix it.
-----Original Message-----
From: Marvin Addison [mailto:[email protected]]
Sent: Monday, August 24, 2009 11:30 AM
To: [email protected]
Subject: Re: [cas-user] Quartz Persistence Error
> method failed; nested exception is org.quartz.JobPersistenceException:
> Couldn't store job:
>
org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean
> [See nested exception: java.io.NotSerializableException:
>
org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean
]
This reads like you're using the feature of Quartz where jobs are
persisted to durable storage, e.g. RDBMS. Is that correct? Can you
share any (redacted) Spring context XML files that you've modified for
your deployment?
Thanks,
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
