468 84.2. Ordering rules / extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 84.3. Available Rules / Extensions . . . same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor

479 84.2. Ordering rules / extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480 84.3. Available Rules / Extensions . . . same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor

479 84.2. Ordering rules / extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480 84.3. Available Rules / Extensions . . . same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor

477 84.2. Ordering rules / extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 84.3. Available Rules / Extensions . . . same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor

477 84.2. Ordering rules / extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 84.3. Available Rules / Extensions . . . same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor

465 83.2. Ordering rules / extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 83.3. Available Rules / Extensions . . . same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor

465 83.2. Ordering rules / extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 83.3. Available Rules / Extensions . . . same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor

464 83.2. Ordering rules / extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 83.3. Available Rules / Extensions . . . same logic applies when mapping a JMS message or a Core message to STOMP. A STOMP 1.0 client can check the presence of the content-length header to determine the type of the message body (String or bytes) tor> The type of this attribute is integer. When this attributed is configured, the broker will check the size of the body of each STOMP frame arrived from connections established with this acceptor

methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line check tool for checking the health of a broker A comma separated string to be passed on to the broker config as network-check-list. The broker will shutdown when all these addresses are unreachable. Using NOTIFY check-period>5check-period> true

0 码力 | 500 页 | 6.37 MB | 1 年前

3

methods for an address' duplicate ID cache to check the cache's size and clear it Support for min/max expiry-delay Per-acceptor security domains Command-line check tool for checking the health of a broker A comma separated string to be passed on to the broker config as network-check-list. The broker will shutdown when all these addresses are unreachable. Using NOTIFY check-period>5check-period> true

0 码力 | 499 页 | 6.37 MB | 1 年前

3