Uploaded image for project: 'MINA'
  1. MINA
  2. DIRMINA-1116

Session Message Order Is Mixed Up Using NioSocketAcceptor

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Trivial
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.1.2
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Environment:
      Windows

      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?

        Attachments

          Activity

            People

            • Assignee:
              johnnyv Jonathan Valliere
              Reporter:
              charlie_boy Charlie
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: