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
I tried to use failover:(xxx)?timeout=xxx, but the stompest does not support this. Then I read the source code and found that some transport options are commented out in src/core/stompest/protocol/failover.py
_SUPPORTED_OPTIONS = {
'initialReconnectDelay': _configurationOption(int, 10)
, 'maxReconnectDelay': _configurationOption(int, 30000)
, 'useExponentialBackOff': _configurationOption(_bool, True)
, 'backOffMultiplier': _configurationOption(float, 2.0)
, 'maxReconnectAttempts': _configurationOption(int, -1)
, 'startupMaxReconnectAttempts': _configurationOption(int, 0)
, 'reconnectDelayJitter': _configurationOption(int, 0)
, 'randomize': _configurationOption(_bool, True)
, 'priorityBackup': _configurationOption(_bool, False)
#, 'backup': _configurationOption(_bool, False), # initialize and hold a second transport connection - to enable fast failover
#, 'timeout': _configurationOption(int, -1), # enables timeout on send operations (in miliseconds) without interruption of reconnection process
#, 'trackMessages': _configurationOption(_bool, False), # keep a cache of in-flight messages that will flushed to a broker on reconnect
#, 'maxCacheSize': _configurationOption(int, 131072), # size in bytes for the cache, if trackMessages is enabled
#, 'updateURIsSupported': _configurationOption(_bool, True), # determines whether the client should accept updates to its list of known URIs from the connected broker
}
The param timeout just be commented out.
I did not find the reasons about this.
Could someone help me explain it ?
The text was updated successfully, but these errors were encountered:
When I wrote the first version of a failover behavior, I copied the failover options from the ActiveMQ website (commented out) and began to implement those I needed most and could make sense of in a client-independent way.
It didn't immediately occur to me as to how one would implement the options which are still commented out in a way which is client-independent (sync, async). Plus, I didn't really need them, so never looked back. If you wish to improve the coverage of failover options, please feel free to open a ticket and/or contribute yourself, be it with code or suggestions.
I tried to use
failover:(xxx)?timeout=xxx
, but thestompest
does not support this. Then I read the source code and found that some transport options are commented out insrc/core/stompest/protocol/failover.py
The param
timeout
just be commented out.I did not find the reasons about this.
Could someone help me explain it ?
The text was updated successfully, but these errors were encountered: