Le 30/05/2014 14:42, Skywalker a écrit : >>>> Check that the response is not sent to another session than teh one > whoch receivedthe message. > > This is exactly what is happening. The response is sent to another session.
So there is (very likely) something in your code that makes the session to be modified. > I modified my ProtocolEncoder & ProtocolDecoder to log its session ids, and > I found out the response to the request came on a differnet session id. > > My question is, is there a way to map the response to its original request? As I said, in the handler, you do session.write(your message), and this very session is propagated to your handler when a message is accepted. If somwhere in yoru code you change the session, then of course, the targetted session willm be different than the session which received the message. Without having your code, it's hard to tell what can happen.
