[AMQCPP-461] Create Thread objects that aren't started can leak their suspended thread on destroy.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.0
• Fix Version/s: 3.6.0
• Component/s: Decaf
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 11/Feb/13 20:42
• Updated: 02/May/13 02:30
• Resolved: 11/Feb/13 20:43

Description

If a Thread object is created but its start method is never called. When destroyed the actual thread can leak if its sitting in the suspended state waiting to be started. This happens right now in the case where a task is submitted to a ThreadPoolExecutor but is rejected for some reason such as the ExecutorService already being shut down. We need to check for the suspended state on destroy and wake the thread with its cancel flag set so it shuts down normally.

Issue Links

• is depended upon by: AMQCPP-451 The number of CMS threads increases when we restart the message broker repeatedly