Hi Sumedha,
With the amount of information available it would be hard to conclude where the error occurs.
Also it would be ideal if there's a way to get disruptor to pin-point the exact location of the Nullpointer when it occurs in the stack trace in it's log exception handler. Will update this thread if i find any.
Let's also make sure to monitor the packets exchanged between the clients since this issue occurs during the protocol handling and converting the bytes[] to a message, so that we could identify whether it's due to a result of malformed packet etc just to make sure.
@Pumudu please add your thoughts. Also could you share the details of the long running tests we did (the type of tests we carried out etc)
Thanks,
Pamod
_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev