Closed ruanpienaar closed 9 years ago
I think this is because the methods in Erlyberly were not synchronized, so multiple calls in could receive responses to different requests. Also found some other issues with reconnect like reapplying traces which are now fixed.
If you find more cases then please reopen.
I'm using Netbeans to compile and startup erlyberly. I noticed the reconnection has a slight hiccup.
Loads of "Not connected"s when the node is down, and then the ominous: "java.lang.ClassCastException: com.ericsson.otp.erlang.OtpErlangTuple cannot be cast to com.ericsson.otp.erlang.OtpErlangList".
Then the "{error,tcollector_down}" keeps happening indefinitely.
I'll look into a fix. ( maybe it's already a known thing ).
Error:
Erlang node is R15B01, and i'm on the erlyberly master branch.