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
In the current implementation of Listener operations, we are not checking the connection subscribe status and directly use ActiveConnections() to register or deregister the listener. However, there might be some edge cases where we don't have a successful connection and still trying to send request messages or vice versa.
Some difference details between Go and Java clients:
Java client removes all the registered entries if there is an error during the invoke call. Go Client does not remove registered entry for ConnectionListenerBinder.regs map. Check if this creates a problem. (See ConnectionListenerBinder#L87)
Java Client keeps the connection objects after registering the listener while Go Client keeps only the ID pairs in map.
The text was updated successfully, but these errors were encountered:
In the current implementation of Listener operations, we are not checking the connection subscribe status and directly use
ActiveConnections()
to register or deregister the listener. However, there might be some edge cases where we don't have a successful connection and still trying to send request messages or vice versa.See the following code section: ConnectionListenerBinder#L123
Some difference details between Go and Java clients:
Java client removes all the registered entries if there is an error during the invoke call. Go Client does not remove registered entry for
ConnectionListenerBinder.regs
map. Check if this creates a problem. (See ConnectionListenerBinder#L87)Java Client keeps the connection objects after registering the listener while Go Client keeps only the ID pairs in map.
The text was updated successfully, but these errors were encountered: