Minor Description
Sometimes when the application closes Wake NettyMessageTransport, and exception is thrown from acceptor.close() call. We catch and log the error and then proceed with the shutdown; this is normal behavior required to make the NettyMessageTransport.close() method idempotent.
The exception does not prevent us from the graceful shutdown of the transport, but it is still unclear what exactly causes the error. Do we close the transport more than once? Does the acceptor gets closed as a side effect of some other service shutdown? The error might be an indicator of some minor error or a race condition somewhere in the REEF/Wake shutdown process.
