[QPID-6846] [Java Broker] IdleTimeoutTicker causes I/O network thread spinning on AMQP 1.0 due to unimplemented heartbeating

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: qpid-java-6.0
• Fix Version/s: qpid-java-6.0
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 13/Nov/15 12:15
• Updated: 13/Nov/15 15:59
• Resolved: 13/Nov/15 15:59

Description

IdleTimeoutTicker maxReadIdle timeout is set to 2 seconds by default. When 2 seconds interval expires, IdleTimeoutTicker initiate heartbeating.

On AMQP 1.0 heartbeating is not implemented, as result, when client application does not send any data, IdleTimeoutTicker can cause an infinite spinning in IO thread due to resetting selector interests which is set to read on selector wake-up. Selector interest continually flips between OP_READ and 0.

We can temporarily disable IdleTimeoutTicker by setting maxReadIdle to 0 until heartbeating is implemented (QPID-6843) in order to work around the issue