[
https://issues.apache.org/jira/browse/DIRMINA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858143#comment-16858143
]
Jonathan Valliere commented on DIRMINA-1116:
--------------------------------------------
So, Flash Player but not RTMP? If it was RTMP the messages would have to be in
order because RTMCS requires correct decoding order. I don't see anywhere why
MINA would be responsible for messages out of order without using an
ExecutorFilter. I'll leave this issue open for another week, if you can't pin
down MINA as the cause of your problem then I will close it.
> 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
> Priority: Trivial
>
> 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]
