Apache ActiveMQ Artemis 1.2.0 User Manual
client and server heartbeats is 500 milliseconds. That means if a client sends a CONNECT frame with heartbeat values lower than 500, the server will defaults the value to 500 milliseconds regardless the values set to 20 seconds. Note Please note that the STOMP protocol version 1.0 does not contain any heartbeat frame. It is therefore the user's responsibility to make sure data is sent within connection-ttl0 码力 | 244 页 | 1.46 MB | 1 年前3- Apache ActiveMQ Artemis 1.3.0 User Manualclient and server heartbeats is 500 milliseconds. That means if a client sends a CONNECT frame with heartbeat values lower than 500, the server will defaults the value to 500 milliseconds regardless the values set to 20 seconds. Note Please note that the STOMP protocol version 1.0 does not contain any heartbeat frame. It is therefore the user's responsibility to make sure data is sent within connection-ttl0 码力 | 247 页 | 1.47 MB | 1 年前3
- Apache ActiveMQ Artemis 1.1.0 User Manualclient and server heartbeats is 500 milliseconds. That means if a client sends a CONNECT frame with heartbeat values lower than 500, the server will defaults the value to 500 milliseconds regardless the values set to 20 seconds. Note Please note that the STOMP protocol version 1.0 does not contain any heartbeat frame. It is therefore the user's responsibility to make sure data is sent within connection-ttl0 码力 | 234 页 | 1.40 MB | 1 年前3
- ActiveMQ Artemis 2.27.1 Documentationmachine should allow keeping GC pauses within 1/3 of session_ms in order to let the Zookeeper heartbeat protocol work reliably. If that is not possible, it is better to increase session_ms , accepting0 码力 | 414 页 | 6.20 MB | 1 年前3
- Apache ActiveMQ Artemis 2.30.0 User Manualmachine should allow keeping GC pauses within 1/3 of session_ms in order to let the Zookeeper heartbeat protocol work reliably. If that is not possible, it is better to increase session_ms , accepting0 码力 | 500 页 | 6.37 MB | 1 年前3
- Apache ActiveMQ Artemis 2.19.0 User Manualmachine should allow keeping GC pauses within 1/3 of session_ms in order to let the Zookeeper heartbeat protocol work reliably. If that is not possible, it is better to increase session_ms , accepting0 码力 | 491 页 | 6.19 MB | 1 年前3
- Apache ActiveMQ Artemis 2.20.0 User Manualmachine should allow keeping GC pauses within 1/3 of session_ms in order to let the Zookeeper heartbeat protocol work reliably. If that is not possible, it is better to increase session_ms , accepting0 码力 | 493 页 | 6.20 MB | 1 年前3
- Apache ActiveMQ Artemis 2.26.0 User Manualmachine should allow keeping GC pauses within 1/3 of session_ms in order to let the Zookeeper heartbeat protocol work reliably. If that is not possible, it is better to increase session_ms , accepting0 码力 | 487 页 | 6.28 MB | 1 年前3
- Apache ActiveMQ Artemis 2.28.0 User Manualmachine should allow keeping GC pauses within 1/3 of session_ms in order to let the Zookeeper heartbeat protocol work reliably. If that is not possible, it is better to increase session_ms , accepting0 码力 | 494 页 | 6.33 MB | 1 年前3
- Apache ActiveMQ Artemis 2.18.0 User Manualmachine should allow keeping GC pauses within 1/3 of session_ms in order to let the Zookeeper heartbeat protocol work reliably. If that is not possible, it is better to increase session_ms , accepting0 码力 | 482 页 | 6.13 MB | 1 年前3
共 24 条
- 1
- 2
- 3