Charlie created DIRMINA-1116:
--------------------------------
Summary: Session Message Order Is Mixed Up Using NioSocketAcceptor
Key: DIRMINA-1116
URL: https://issues.apache.org/jira/browse/DIRMINA-1116
Project: MINA
Issue Type: Bug
Components: Core
Affects Versions: 2.1.2
Environment: Windows
Reporter: Charlie
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:
{code:java}
//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);{code}
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?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
