[DIRMINA-1116] Session Message Order Is Mixed Up Using NioSocketAcceptor

• Type: Bug
• Status: Resolved
• Priority: Trivial
• Resolution: Cannot Reproduce
• Affects Version/s: 2.1.2
• Component/s: Core
• Environment: Windows
• Assignee: Jonathan Valliere
• Reporter: Charlie
• Created: 02/Jun/19 18:44
• Updated: 15/Apr/20 15:55
• Resolved: 15/Apr/20 15:55

Description

The application requires clients to send communications in a specific sequence.

For some reason the messages received by a session sometimes get processed out of order by MINA.

Here is my usage of MINA:

//Setup filter chain
DefaultIoFilterChainBuilder chain;
acceptor = new NioSocketAcceptor(Runtime.getRuntime().availableProcessors() + 1);
 chain = acceptor.getFilterChain();
 chain.addLast("codec", new ProtocolCodecFilter(new ApplicationProtocolCodecFactory()));
 chain.addLast("authentication", new AuthenticationFilter());
 chain.addLast("inputVerification", new InputValidatorFilter());
acceptor.setHandler(handler);

The messages are already out of order in the protocol decoder filter.

The client application sends messages using one thread and uses tcp so it can't be sending out of order.

Is this intended behavior due to the async model?