some JVM settings for tuning the garbage collection policy and heap size. We recommend using a parallel garbage collection algorithm to smooth out latency and minimise large GC pauses. By default Apache server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

some JVM settings for tuning the garbage collection policy and heap size. We recommend using a parallel garbage collection algorithm to smooth out latency and minimise large GC pauses. By default Apache server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

some JVM settings for tuning the garbage collection policy and heap size. We recommend using a parallel garbage collection algorithm to smooth out latency and minimise large GC pauses. By default Apache server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

set some JVM settings for tuning the garbage collection policy and heap size. We recommend using a parallel garbage collection algorithm to smooth out latency and minimise large GC pauses. By default Apache server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port? key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

some JVM settings for tuning the garbage collection policy and heap size. We recommend using a parallel garbage collection algorithm to smooth out latency and minimise large GC pauses. By default Apache server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport Netty transport. Using JMS 55 Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

some JVM settings for tuning the garbage collection policy and heap size. We recommend using a parallel garbage collection algorithm to smooth out latency and minimise large GC pauses. By default Apache server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport Netty transport. Using JMS 36 Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

some JVM settings for tuning the garbage collection policy and heap size. We recommend using a parallel garbage collection algorithm to smooth out latency and minimise large GC pauses. By default Apache server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport Netty transport. Using JMS 36 Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

some JVM settings for tuning the garbage collection policy and heap size. We recommend using a parallel garbage collection algorithm to smooth out latency and minimise large GC pauses. By default Apache server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport Netty transport. Using JMS 36 Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

some JVM settings for tuning the garbage collection policy and heap size. We recommend using a parallel garbage collection algorithm to smooth out latency and minimise large GC pauses. By default Apache server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport Netty transport. Using JMS 55 Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445

set some JVM settings for tuning the garbage collection policy and heap size. We recommend using a parallel garbage collection algorithm to smooth out latency and minimise large GC pauses. By default Apache server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port? key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445