Spring Boot - Async ProcessingWhat happens when the task queue is full and the thread pool has reached its maximum size in Spring Boot's ThreadPoolTaskExecutor?ANew tasks are queued indefinitelyBNew tasks are rejected and an exception is thrownCThe thread pool automatically increases max sizeDTasks are executed on the main threadCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand thread pool rejection policyWhen max threads and queue are full, new tasks are rejected.Step 2: Identify default behavior in Spring BootBy default, ThreadPoolTaskExecutor throws RejectedExecutionException on rejection.Final Answer:New tasks are rejected and an exception is thrown -> Option BQuick Check:Full pool + queue = task rejection [OK]Quick Trick: Full pool rejects new tasks with exception [OK]Common Mistakes:Assuming queue grows indefinitelyThinking thread pool auto-expands max sizeBelieving tasks run on main thread automatically
Master "Async Processing" in Spring Boot9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallPerf
More Spring Boot Quizzes API Documentation - Grouping APIs by tags - Quiz 9hard API Documentation - Why API docs matter - Quiz 13medium Async Processing - Cron expressions for scheduling - Quiz 4medium Async Processing - Why async processing matters - Quiz 1easy Caching - @CacheEvict for invalidation - Quiz 2easy Caching - Cache configuration - Quiz 4medium Caching - @CachePut for updating cache - Quiz 12easy Caching - @EnableCaching annotation - Quiz 4medium Docker and Deployment - Database and app orchestration - Quiz 7medium Testing Spring Boot Applications - Test profiles and configuration - Quiz 1easy