journal. The files on this journal are prefixed as activemq-bindings . Each file has a bindings extension. File size is 1048576 , and it is located at the bindings folder. Persistence 158 Message journal Java platform. The files on this journal are prefixed as activemq-data . Each file has an amq extension. File size is by the default 10485760 (configurable), and it is located at the journal folder When used on an acceptor the sniHost is a regular expression used to match the server_name extension on incoming SSL connections. If the name doesn't match then the connection to the acceptor will

journal. The files on this journal are prefixed as activemq-bindings . Each file has a bindings extension. File size is 1048576 , and it is located at the bindings folder. Persistence 155 Message journal Java platform. The files on this journal are prefixed as activemq-data . Each file has an amq extension. File size is by the default 10485760 (configurable), and it is located at the journal folder When used on an acceptor the sniHost is a regular expression used to match the server_name extension on incoming SSL connections. If the name doesn't match then the connection to the acceptor will

journal. The files on this journal are prefixed as activemq-bindings . Each file has a bindings extension. File size is 1048576 , and it is located at the bindings folder. Persistence 158 Message journal Java platform. The files on this journal are prefixed as activemq-data . Each file has an amq extension. File size is by the default 10485760 (configurable), and it is located at the journal folder When used on an acceptor the sniHost is a regular expression used to match the server_name extension on incoming SSL connections. If the name doesn't match then the connection to the acceptor will

CLIENT_ID is the JMS client ID. SNI_HOST is the hostname indicated by the client in the SNI extension of the TLS protocol. SOURCE_IP is the source IP address of the client. USER_NAME is the username journal. The files on this journal are prefixed as activemq-bindings. Each file has a bindings extension. File size is 1048576, and it is located at the bindings folder. • Message journal. This journal any Java platform. The files on this journal are prefixed as activemq-data. Each file has an amq extension. File size is by the default 10485760 (configurable), and it is located at the journal folder.

CLIENT_ID is the JMS client ID. SNI_HOST is the hostname indicated by the client in the SNI extension of the TLS protocol. SOURCE_IP is the source IP address of the client. USER_NAME is the username journal. The files on this journal are prefixed as activemq-bindings. Each file has a bindings extension. File size is 1048576, and it is located at the bindings folder. • Message journal. This journal any Java platform. The files on this journal are prefixed as activemq-data. Each file has an amq extension. File size is by the default 10485760 (configurable), and it is located at the journal folder.

CLIENT_ID is the JMS client ID. SNI_HOST is the hostname indicated by the client in the SNI extension of the TLS protocol. SOURCE_IP is the source IP address of the client. USER_NAME is the username journal. The files on this journal are prefixed as activemq-bindings. Each file has a bindings extension. File size is 1048576, and it is located at the bindings folder. • Message journal. This journal any Java platform. The files on this journal are prefixed as activemq-data. Each file has an amq extension. File size is by the default 10485760 (configurable), and it is located at the journal folder.

CLIENT_ID is the JMS client ID. SNI_HOST is the hostname indicated by the client in the SNI extension of the TLS protocol. SOURCE_IP is the source IP address of the client. USER_NAME is the username journal. The files on this journal are prefixed as activemq-bindings. Each file has a bindings extension. File size is 1048576, and it is located at the bindings folder. • Message journal. This journal any Java platform. The files on this journal are prefixed as activemq-data. Each file has an amq extension. File size is by the default 10485760 (configurable), and it is located at the journal folder.

CLIENT_ID is the JMS client ID. SNI_HOST is the hostname indicated by the client in the SNI extension of the TLS protocol. SOURCE_IP is the source IP address of the client. USER_NAME is the username journal. The files on this journal are prefixed as activemq-bindings. Each file has a bindings extension. File size is 1048576, and it is located at the bindings folder. • Message journal. This journal any Java platform. The files on this journal are prefixed as activemq-data. Each file has an amq extension. File size is by the default 10485760 (configurable), and it is located at the journal folder.

CLIENT_ID is the JMS client ID. SNI_HOST is the hostname indicated by the client in the SNI extension of the TLS protocol. SOURCE_IP is the source IP address of the client. USER_NAME is the username journal. The files on this journal are prefixed as activemq-bindings. Each file has a bindings extension. File size is 1048576, and it is located at the bindings folder. • Message journal. This journal any Java platform. The files on this journal are prefixed as activemq-data. Each file has an amq extension. File size is by the default 10485760 (configurable), and it is located at the journal folder.

CLIENT_ID is the JMS client ID. SNI_HOST is the hostname indicated by the client in the SNI extension of the TLS protocol. SOURCE_IP is the source IP address of the client. USER_NAME is the username journal. The files on this journal are prefixed as activemq-bindings. Each file has a bindings extension. File size is 1048576, and it is located at the bindings folder. • Message journal. This journal any Java platform. The files on this journal are prefixed as activemq-data. Each file has an amq extension. File size is by the default 10485760 (configurable), and it is located at the journal folder.