Merge pull request #1896 from clebertsuconic/2.3.x

test fix on TemporaryQueueTest
BZ-1152410 - handle rollback called twice

https://bugzilla.redhat.com/show_bug.cgi?id=1152410

There are 2 parts to this, firstly make sure that if the call to rollback fails make sure that the session and consumers re restarted.

secondly at the server make sure that we dont cancel the refs and add them to the already rolled back tx, we should handle them separately and rollback on to the queue in a new tx.
Merge pull request #1914 from andytaylor/2.3.x

BZ-1152410 - handle rollback called twice
HORNETQ-1437  Keep JNDI when destroying JMS queues

Change the semantics of the destroyTopic(java.lang.String) and
destroyQueue(java.lang.String) methods on
org.hornetq.api.jms.management.JMSServerControl so that if consumers
are attached to the topic/queue then the JNDI bindings are not removed.
Merge pull request #1926 from jbertram/2.3.x

HORNETQ-1437  Keep JNDI when destroying JMS queues
Fix tests broken from HORNETQ-1437
Merge pull request #1931 from jbertram/2.3.x

Fix tests broken from HORNETQ-1437
HORNETQ-1374 - Ability to close all consumers on a destination and the connections for these consumers

Conflicts:
	hornetq-server/src/main/java/org/hornetq/core/management/impl/HornetQServerControlImpl.java
	hornetq-server/src/main/java/org/hornetq/core/server/HornetQMessageBundle.java
	hornetq-server/src/main/java/org/hornetq/core/server/HornetQServerLogger.java
HORNETQ-1373 - Ability to terminate a connection by JMS User
Fix tests and logging for HORNETQ-1373 and HORNETQ-1374
Merge pull request #1935 from jbertram/2.3.x

Couple of new admin functions
JBPAPP-11022 Remove unnecessary WARN log part II

This is really when a newer server connects to the client