[DIRMINA-639] WriteFuture are updated long after a session.write() is done

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Won't Fix
• Affects Version/s: 2.0.0-M3
• Fix Version/s: 2.0.8
• Assignee: Unassigned
• Reporter: Emmanuel Lécharny
• Created: 20/Nov/08 18:42
• Updated: 05/Sep/14 12:15
• Resolved: 05/Sep/14 12:15

Description

While expecting the writeFuture to be updated when the write has been done, it's done only when we get out of the chain. This is a major problem as you can't rely on this to bail a connection based on a slow client. Typically, we may stack thousands of message into the writeQueuebuffer, as the flush is only done when we have gone though the whole chain, and back.

The only way to get the data be blushed immediately is to add an executorFilter on the WRITE eventType, in order to create a new thread to handle this flush, otherwise we have to wait for the current processor to be done with the chain processing.