[
https://issues.apache.org/jira/browse/DIRMINA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858042#comment-16858042
]
Charlie commented on DIRMINA-1116:
----------------------------------
This issue does sound wrong, since in tcp the data is coming in as a stream of
bytes. Unless mina is doing some slicing (and let me say that would have to be
some intricate slicing since I dont get corrupt messages), then the issue would
have to be in the decoder, yet it happens while the decoder is re-constructing
the message from bytes.
If it's not mina then the only other explanation is some bug in flash player,
since the entire client program is single threaded and it literally writes the
packet id to the socket then the data and flushes. The documentation does say
flushing doesnt ensure the data is sent at that moment. Maybe it does something
odd there and doesn't send written bytes in the order they were "flushed".
Thanks for the help.
> 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: Major
>
> 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]
