I added try {...} catch (Exception e) { log.error(e.getMessage(); throw e; }
around the code. I can't see any error messages in the logs since I made
that change. But in the encode method just before that try catch block I
have log.warn("Encoding!") line, which is not being reached or outputted
mos
On 3/24/10 1:33 AM, Erinc Arikan wrote:
Sure; but before doing so I am wondering what will happen if the client
sends a message and disconnects while I was intending to send
acknowledgement back, will I receive the same null pointer exception?
no, I don't think so, from the top of my head. Ho
Sure; but before doing so I am wondering what will happen if the client
sends a message and disconnects while I was intending to send
acknowledgement back, will I receive the same null pointer exception?
Because in the past whenever I had a problem in the response encoder, I used
to see it in the s
On 3/24/10 12:08 AM, Erinc Arikan wrote:
I am using MINA 2.0.0.RC1, I built my own protocol codec filter to deal with
messages. All of my tests went fine in test environments and I went live
recently. I am processing almost a message every second.
The issue that I experienced in the production e
I am using MINA 2.0.0.RC1, I built my own protocol codec filter to deal with
messages. All of my tests went fine in test environments and I went live
recently. I am processing almost a message every second.
The issue that I experienced in the production environment is random null
pointer exception
