Getting the same issue using ExAWS and SQS. We just migrated our app from Heroku (Elixir 1.7.4 OTP 20.3) to AWS, upgrading at the same time the OTP version to 21.3 keeping the same Elixir version. We never saw this issue on Heroku.
antoniobg
outlog
21.3 also had a ssl bug.. please try with latest patch release.. eg 21.3.8.3
you didn’t see it on heroku as you were using OTP 20.3
1
outlog
@antoniobg seems like it’s tracked here: unhandled `{ssl_closed, _}` message when using `async` · Issue #464 · benoitc/hackney · GitHub - and that there is a current workaround of implementing
def handle_info({:ssl_closed, _msg}, state), do: {:noreply, state}
you could also consider using a different http client say HTTPotion:
0
amarandon
I’ve added a catch-all handle_info to my GenServer which calls HTTPoison functions, as suggested in the previous message, but I’m still getting the error. Did you put this in your GenServer or somewhere else?
I’m not sure if I did it properly though because I don’t really understand what’s going on. What is a “message leak”?
0
chulkilee
@amarandon could you make sure you added handle_info callback where you call those libraries (and thus start a process from it)?
- Process A calls HTTP lib func (e.g. HTTPoison or Tesla) synchronously
- HTTP lib func behind the scene starts a process B to handle HTTP connection
- When HTTP request is completed… HTTP lib func returns the result (in process A)
The problem is, for some reason process B (which should be hidden from process A point of view) sends those messages to process A - so it’s “leaking”.
1