Spring Boot集群单实例调度器问题：ShedLock启动类型转换异常求助

Hey there, let's break down why you're hitting this ClassCastException and how to fix it straight away!

The Root Cause #

When you use ShedLock's SpringLockableTaskSchedulerFactoryBean, it doesn't return a raw ThreadPoolTaskScheduler instance. Instead, it creates a proxy wrapper (SpringLockableTaskScheduler) that layers distributed locking logic on top of your original scheduler. Trying to cast this proxy directly to ThreadPoolTaskScheduler fails because the proxy only implements the TaskScheduler interface, not the concrete class.

Solutions to Try #

1. Inject the TaskScheduler Interface (Simplest Fix)

If you don't need specific methods exclusive to ThreadPoolTaskScheduler, just switch your injection to the TaskScheduler interface:

// Before (causes ClassCastException)
@Autowired
private ThreadPoolTaskScheduler taskScheduler;

// After (works correctly with ShedLock's proxy)
@Autowired
private TaskScheduler taskScheduler;

The SpringLockableTaskScheduler proxy fully implements TaskScheduler, so all your scheduling operations will work as expected while retaining ShedLock's locking functionality.

2. Access the Original ThreadPoolTaskScheduler If Needed

If you absolutely require methods only available on ThreadPoolTaskScheduler (like getThreadPoolExecutor() to manage the thread pool), extract the original scheduler from the proxy:

@Autowired
private TaskScheduler taskScheduler;

public void manageThreadPool() {
    if (taskScheduler instanceof SpringLockableTaskScheduler) {
        // Pull out the wrapped original scheduler
        ThreadPoolTaskScheduler originalScheduler = 
            (ThreadPoolTaskScheduler) ((SpringLockableTaskScheduler) taskScheduler).getTargetTaskScheduler();
        
        // Now you can use methods like getThreadPoolExecutor()
        ExecutorService executor = originalScheduler.getThreadPoolExecutor();
        // ... perform thread pool management operations here
    }
}

⚠️ Critical Note: Never use the original scheduler to run scheduled tasks—those tasks won't be protected by ShedLock's distributed locks, defeating the purpose of using ShedLock in the first place.

3. Correct Your Scheduler Bean Configuration

If you're manually defining the scheduler bean in a config class, avoid casting the factory bean's output to ThreadPoolTaskScheduler. Here's the proper setup:

@Configuration
public class ShedLockConfig {

    @Bean
    public LockProvider lockProvider(DataSource dataSource) {
        return new JdbcTemplateLockProvider(dataSource);
        // Swap this for your preferred lock provider (Redis, ZooKeeper, etc.)
    }

    // Define the raw ThreadPoolTaskScheduler first
    @Bean
    public ThreadPoolTaskScheduler originalTaskScheduler() {
        ThreadPoolTaskScheduler scheduler = new ThreadPoolTaskScheduler();
        scheduler.setPoolSize(5); // Adjust pool size to match your needs
        scheduler.setThreadNamePrefix("shedlock-scheduler-");
        scheduler.initialize();
        return scheduler;
    }

    // Wrap the raw scheduler with ShedLock's locking logic
    @Bean
    public TaskScheduler lockedTaskScheduler(ThreadPoolTaskScheduler originalTaskScheduler, LockProvider lockProvider) {
        SpringLockableTaskSchedulerFactoryBean factory = new SpringLockableTaskSchedulerFactoryBean();
        factory.setLockProvider(lockProvider);
        factory.setTargetTaskScheduler(originalTaskScheduler);
        return factory.getObject();
    }
}

Now you can inject lockedTaskScheduler for lock-protected scheduled tasks, or originalTaskScheduler when you need the raw concrete class for non-scheduling operations.

Quick Compatibility Check #

Ensure your ShedLock version matches your Spring Boot version. Mismatched versions can cause unexpected proxying issues:

• Spring Boot 3.x → Use ShedLock 5.x+
• Spring Boot 2.x → Use ShedLock 4.x

内容的提问来源于stack exchange，提问作者Sumit