> The exception I've provided is not complete, there is also: > > Caused by: java.lang.NullPointerException > at foo.MyDecoder.doDecode(...) > > The line where it occurs looks like: > > int var = (Integer) session.getAttribute(ATTRIBUTE_CONSTANT_NAME); > > Do you still need an exception dumped at line 234 of the > ProtocolCodecFilter? What additional information it may provide?
No, it's enough. Here, your session is null. You may have to check that in your decoder. Now, the reason why the session has been "nulled" has to be understood. AFAIK, even if the client brutally close the session, this might happen. However, I think we should have a mechanism handling such a case, like if there is a message being processed by this session, then the session must be marked as 'closing', not set to null. I will try to look at this problem this evening... In the mean time, a simple check on session could help... -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
