ARTEMIS-611 adjust ttlMin to fix Stomp tests
This commit is contained in:
parent
707b51796a
commit
4232ed70d4
|
@ -269,7 +269,7 @@ public class StompFrameHandlerV11 extends VersionedStompFrameHandler implements
|
|||
long ttlMax = ttlMaxStr == null ? Long.MAX_VALUE : Long.valueOf(ttlMaxStr);
|
||||
|
||||
String ttlMinStr = (String) connection.getAcceptorUsed().getConfiguration().get(TransportConstants.CONNECTION_TTL_MIN);
|
||||
long ttlMin = ttlMinStr == null ? 500 : Long.valueOf(ttlMinStr);
|
||||
long ttlMin = ttlMinStr == null ? 1000 : Long.valueOf(ttlMinStr);
|
||||
|
||||
String heartBeatToTtlModifierStr = (String) connection.getAcceptorUsed().getConfiguration().get(TransportConstants.HEART_BEAT_TO_CONNECTION_TTL_MODIFIER);
|
||||
double heartBeatToTtlModifier = heartBeatToTtlModifierStr == null ? 2 : Double.valueOf(heartBeatToTtlModifierStr);
|
||||
|
|
|
@ -320,7 +320,7 @@ not to be considered late and trigger a disconnect.
|
|||
|
||||
The minimum and maximum connection TTL allowed can also be specified on the
|
||||
acceptor via the `connectionTtlMin` and `connectionTtlMax` properties respectively.
|
||||
The default `connectionTtlMin` is 500 and the default `connectionTtlMax` is Java's
|
||||
The default `connectionTtlMin` is 1000 and the default `connectionTtlMax` is Java's
|
||||
`Long.MAX_VALUE` meaning there essentially is no max connection TTL by default.
|
||||
Keep in mind that the `heartBeatConnectionTtlModifer` is relevant here. For
|
||||
example, if a client sends a `heart-beat` header of `20000,0` and the acceptor
|
||||
|
|
Loading…
Reference in New Issue