[NIFI-2626] LIstenHTTP leaks threads when address is already in use

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0, 0.7.1
• Component/s: Core Framework
• Assignee: Jeff Storck
• Reporter: Jeff Storck
• Created: 22/Aug/16 18:36
• Updated: 07/Oct/16 18:59
• Resolved: 22/Aug/16 20:01

Description

While testing the current 1.0.0 master branch for release, I ran into a thread leak issue with ListenHTTP. Though not the fault of ListenHTTP explicitly, threads are being leaked by Jetty after attempting to bind to an address that is already in use. Jetty starts a thread when server.start() is called, but does not clean up after itself if the start() method throws an exception. Over time, these threads pile up and eventually the JVM will run out of memory.

Issue Links

• links to: GitHub Pull Request #910