[CAMEL-11179] MultiThread race condition in DefaultShutdownStrategy for suspend/resume

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 2.18.3
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Benjamin Graf
• Created: 20/Apr/17 18:28
• Updated: 20/Jul/17 08:11
• Resolved: 20/Jul/17 08:11

Description

If call to suspend with timeout does timeout than two threads are invoking forced processing one for suspending and one for hard stopping. This causes the Consumer to be possibly left in a dead state.

E.g. Jms consuming route:

1. Timeout occurs, ShutdownTask gets completed before main thread
   -> JmsConsumer gets stopped (listener gets destroyed), resume has no effect
2. Timeout occurs, ShutdownTask get completet after main thread
   -> JmsConsumer gets stopped first (listener gets destroyed) and get suspended second, resume sets Consumer to started but the listener is still destroyed!