Hi Frédéric, On 5/3/07, Frédéric Brégier <[EMAIL PROTECTED]> wrote:
One remark, possibly erroneous, so correct me if I am wrong: TCP ensures that packet will arrive in the same order on the server side as they were sent by the client but then if there are threads, nothing ensure you that they are managed in this order once MINA has created the thread process (in the filter logic I mean).
Yes, MINA needs to maintain the order of the fired events, and it does already in ExecutorFilter. <snip/>
I have seen this using a demux io handler. One client send a first message, generating a new thread, then send the next message (possibly a different type of message) and generating again a new thread on the server side. Then, sometimes (on multi processor servers) I saw the second thread finishing its work before the first one (the business logic was less on the second message than the first message of course).
Which version of MINA are you using? There was a related bug in branches/1.1, but it has been fixed in the latest releases. Please let me know how to if you can reproduce the problem. Thanks, Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
