[QPIDJMS-416] Move protocol processing work into the netty event loop thread

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.37.0
• Fix Version/s: 0.38.0
• Component/s: qpid-jms-client
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 09/Oct/18 19:27
• Updated: 16/Nov/18 10:17
• Resolved: 11/Oct/18 15:10

Description

Currently the protocol specific processing is handled in its own single threaded executor which creates a performance drop as reads and writes are queued into Netty for handling.  We can achieve a significant performance boost by handling all the protocol work inside the Netty event loop and not hopping between threads as we do now. 

This requires some refactoring of connect and shutdown logic and some safeguards around all callbacks in the transport to ensure that we always operate on the event loop and not one on a client thread.