Continued the search. Had a intensive look at my encoder class
de.root1.simon.codec.base.AbstractMessageEncoder.
You recommended checking the buffer and to ensure it is cleared... The
used buffer is created every time from scratch. So it's a new buffer,
everytime.
I observed the buffer which is beeing sent. Looks like the data which is
sent is always okay.
On receiving side (exception complains about decoding...) it seems that
the begin of a message is somewhen not correctly determined, but only if
a) cpu ist fast enough (I'm not able to reproduce it on my rather slow
home server (AMD 2x1,6Ghz)
b) logging does not slow down too much
The "no appropriate message decoder" message show a big amount of bytes.
When analyzing them, it seems that it contains multiple messages, but
beginning somewhere in the middle of a message.
Feels like I'm getting closer.
Am 14.07.2016 um 08:24 schrieb Alexander Christian:
Am 13.07.2016 um 16:55 schrieb Emmanuel Lécharny:
This is clearly some serialized java class. I also looked at the buffer,
and I saw the class names in it.
Nothing bad here.
yes, nothing bad. But gives an indication where to continue the search.
