Fair enough. I double checked with the other person who was working on this on our production night (and who has more legacy app knowledge and more WebLogic knowledge than I do), and we do not have to persist to a database, however when we turned the database persistence off and started using disk instead (not in-memory, which we haven't tried), we still got a failure. We also cannot recreate the failure in our development environment, which makes this extra-difficult to deal with. At the moment, we've commented out the ticket registry cleaner part of ticketRegistry.xml. While we are in production, this is an alpha release.
From: Scott Battaglia [mailto:[email protected]] Sent: Monday, August 24, 2009 12:28 PM To: [email protected] Subject: Re: [cas-user] Quartz Persistence Error On Mon, Aug 24, 2009 at 12:20 PM, Kimberly Ennis <[email protected]> wrote: <snip /> 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. I doubt most people try and persist the Quartz job. Its a relatively non-critical job if you're using In-Memory storage (because if your CAS server goes down then you've lost everything in memory anyway ;-)) Cheers, Scott -----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 -- 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
