Lack of detection of EOF (No automatic reconnection) about stompngo HOT 4 CLOSED

Agreed that something more needs to be done when EOF is received attempt to accurately notify the caller. Thanks for the report.

I'll think about it this weekend. It might be more complex than just close(c.input) when the reader goroutine exits, especially for a 1.1 client.

Note however: reconnects, retries, fail overs, etc are totally a caller's responsibility.

from stompngo.

This is a very specific example of a more general problem.

Problem statement: package users are not being properly notified of network errors (including EOF) encountered during a read from the underlying net.Conn or tls.Conn.

The fix for this will address the general problem, including the specific case reported.

from stompngo.

Fixed: f0f8470

The read from the subscribe channel should complete with a MessageData that has a non-nil Error. In the particular case described, Error.Error() should be EOF.

Note that the package will subsequently treat this connection instance as dead, and no further operations may be performed with it.

from stompngo.

If you are still using the stompngo package please try the current v.1.0.2 tag.

Tag information:

b1f1d96 refs/tags/v1.0.2

Document that version number in any issue reports.

Thanks for the support.

Guy

from stompngo.