improve tearDown
HORNETQ-891
The fix enables a user to configure a stomp acceptor with a customized connection-ttl.
HORNETQ-899
    Adding a 'stomp-enable-message-id' parameter to stomp acceptors so that each stomp
    message can have a unique id to facilitate message browsing.
Fix findbugs warnings
log warning if could not read 'length bytes, delete unused methods (wasn't caught before due to lack of @Override)
RejectedExecutionException is expected on server.stop() so don't log stacktraces due to it
Avoid leaking threads: stop trying to receive if executor is being shutdown.
delete dead code, and some cleaning
Fix dead lock: causeExit() could block while ClientSessionFactoryImpl.connect()
tried to force the first ping, at ClientSessionFactoryImpl$PingRunnable.send(.)

The code to cancel this ping would not get reached. See stack trace below:

org.hornetq.core.client.impl.ClientSessionFactoryImpl.causeExit(ClientSessionFactoryImpl.java:442)
org.hornetq.core.client.impl.ServerLocatorImpl$StaticConnector$Connector.disconnect(ServerLocatorImpl.java:1792)
org.hornetq.core.client.impl.ServerLocatorImpl$StaticConnector.disconnect(ServerLocatorImpl.java:1719)
org.hornetq.core.client.impl.ServerLocatorImpl.doClose(ServerLocatorImpl.java:1259)
org.hornetq.core.client.impl.ServerLocatorImpl.close(ServerLocatorImpl.java:1227)
org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$1.run(ClusterConnectionImpl.java:470)
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
===============================================================================
Thread Thread[Thread-3 (HornetQ-server-HornetQServerImpl::NettySymmetricClusterWithBackupTest/Live(3)-1394697488),5,HornetQ-server-HornetQServerImpl::NettySymmetricClusterWithBackupTest/Live(3)-1394697488] name = Thread-3 (HornetQ-server-HornetQServerImpl::NettySymmetricClusterWithBackupTest/Live(3)-1394697488) id = 56499 group = java.lang.ThreadGroup[name=HornetQ-server-HornetQServerImpl::NettySymmetricClusterWithBackupTest/Live(3)-1394697488,maxpri=10]

org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.flush(RemotingConnectionImpl.java:456)
org.hornetq.core.client.impl.ClientSessionFactoryImpl$PingRunnable.send(ClientSessionFactoryImpl.java:1687)
org.hornetq.core.client.impl.ClientSessionFactoryImpl.getConnection(ClientSessionFactoryImpl.java:1317)
org.hornetq.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:1012)
org.hornetq.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:230)
org.hornetq.core.client.impl.ServerLocatorImpl$StaticConnector$Connector.tryConnect(ServerLocatorImpl.java:1772)
org.hornetq.core.client.impl.ServerLocatorImpl$StaticConnector.connect(ServerLocatorImpl.java:1608)
org.hornetq.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:572)
org.hornetq.core.client.impl.ServerLocatorImpl$3.run(ServerLocatorImpl.java:545)
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
Use latch to signal session creation instead of wait/notify.
Fix javadoc warning
maven: javac to show warnings
Merge pull request #43 from gaohoward/master

HORNETQ-891
Merge pull request #46 from FranciscoBorges/master

1 dead lock fixed, 1 thread leak fixed, finally cleaned all concurrency control in ClientSessionFactory