ARTEMIS-601 some documentation changes around reload

docs/user-manual/en/SUMMARY.md

@@ -17,6 +17,7 @@
 * [Filter Expressions](filter-expressions.md)
 * [Persistence](persistence.md)
 * [Configuring Transports](configuring-transports.md)
+* [Configuration Reload](config-reload.md)
 * [Detecting Dead Connections](connection-ttl.md)
 * [Detecting Slow Consumers](slow-consumers.md)
 * [Resource Manager Configuration](transaction-config.md)

docs/user-manual/en/config-reload.md

@@ -0,0 +1,13 @@
+# Configuration Reload
+
+The system will perform a periodic check on the configuration files, configured by `configuration-file-refresh-period`, with the default at 5000, in milliseconds.
+
+Once the configuration file is changed (broker.xml) the following modules will be reloaded automatically:
+
+- Address Settings
+- Security Settings
+- JMS Queues
+- JMS Topics
+
+
+Notice: Queues and Topics won't be removed upon reload, given the risk of losing messages. You may execute explicit CLI or Management operations to remove destinations.

docs/user-manual/en/configuration-index.md

@@ -30,6 +30,7 @@ Name | Description
 [bindings-directory](persistence.md "Configuring the bindings journal")  | The folder in use for the bindings folder
 [bridges](core-bridges.md "Core Bridges")  | [a list of bridge](#bridge-type)
 [broadcast-groups](clusters.md "Clusters")                                            | [a list of broadcast-group](#broadcast-group-type)
+[configuration-file-refresh-period](config-reload.md) |  The frequency in milliseconds the configuration file is checked for changes (default 5000)
 [check-for-live-server](ha.md)   |  Used for a live server to verify if there are other nodes with the same ID on the topology
 [cluster-connections](clusters.md "Clusters") |  [a list of cluster-connection](#cluster-connection-type)
 [cluster-password](clusters.md "Clusters")                                                                                              |   Cluster password. It applies to all cluster configurations.

docs/user-manual/en/connection-ttl.md

@@ -69,6 +69,21 @@ finally
 }
 ```
 
+
+Or with using auto-closeable feature from Java, which can save a few lines of code:
+
+``` java
+
+
+try (
+     ActiveMQConnectionFactory jmsConnectionFactory = new ActiveMQConnectionFactory();
+     Connection jmsConnection = jmsConnectionFactory.createConnection())
+{
+   ... do some stuff with the connection...
+}
+```
+
+
 Unfortunately users don't always write well behaved applications, and
 sometimes clients just crash so they don't have a chance to clean up
 their resources!
@@ -205,4 +220,4 @@ thread adds a little more latency. These packets are:
 
 To disable asynchronous connection execution, set the parameter
 `async-connection-execution-enabled` in `broker.xml` to
-`false` (default value is `true`).
+`false` (default value is `true`).