[erlang-questions] R1502 ssl dropping byte(s)?
Fri Nov 2 19:27:25 CET 2012
Thank you, I've checked the thread.
However, if I understand correctly, your problem was fragmentation.
I don't have that kind of problem. I.e. I have a code which handles
fragmentation, and it doesn't bother me if a short message is fragmented.
Theoretically, the message can be fragmented in one byte micro-messages,
and I will still recompose it correctly
My problem arises because after the receive timeout occurs, one byte is
simply missing i.e. it is not received on the next ssl:recv call.
On Fri, Nov 2, 2012 at 6:49 PM, Dmitry Kolesnikov <>wrote:
> I also had an issue with a first byte in ssl.
> Please check this thread:
> This could be a reason for your case as well.
> - Dmitry
> On Nov 2, 2012, at 7:33 PM, sasa wrote:
> > Hello,
> > Today I have migrated my production servers to R15B02 (previously they
> ran on R14).
> > Generally, everything works fine. However, I do notice a strange
> behavior occasionally.
> > I'm not sure if Erlang is to blame, but it's a strange coincidence that
> this started occurring after the migration, and system is in production for
> almost two years.
> > In my system, I am constantly fetching some data from the external
> provider via ssl. The code is roughly following:
> > loop(Socket) ->
> > ssl:recv(Socket, 0, 5000),
> > ...
> > loop(Socket).
> > After switching to R15, I have noticed that occasionally, a byte gets
> "lost". This always happens after 5 or 10 seconds which leads me to
> suspicion, that possibly some race condition occurs in ssl.
> > Could it be that the timeout occurs just as the bytes start to arrive,
> and the first one is discarded?
> > Again, I didn't notice this behavior on R14.
> > Best regards,
> > Sasa
> > _______________________________________________
> > erlang-questions mailing list
> > http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions