You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the recent change to formalize the exception path through existing end-points and in-flight messages, we didn't also look at the paths to create new end-points.
Ideally, this would be documented to throw this new exception, as well.
The text was updated successfully, but these errors were encountered:
@ChrisGreenaway@myronkscott : I am linking this with #215 also because we also ran into this issue. We are always using timed out invokations for voltron and when voltron closes the connection, we have no way to know and if we do a connection.getEntityRef(), it will block indefinitely.
So if we had #215 in place, we could know that the connection is closed and that we cannot use it.
During the recent change to formalize the exception path through existing end-points and in-flight messages, we didn't also look at the paths to create new end-points.
Ideally, this would be documented to throw this new exception, as well.
The text was updated successfully, but these errors were encountered: