[ https://issues.apache.org/jira/browse/DIRMINA-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Valliere resolved DIRMINA-1116. ---------------------------------------- Assignee: Jonathan Valliere Resolution: Cannot Reproduce If MINA was sending messages out of order the entire ecosystem would be complaining about it. This is most likely a problem with the Reporter's code. For the time being, I am resolving this issue. If new information becomes available then it can be reopened. > 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 > Assignee: Jonathan Valliere > 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 (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org