stacktraces appear in log when upgrading from 2.2.2 -> 2.2.21

[stuarthalloway]

While troubleshooting this issue I temporarily upgraded to a more recent (2.2.21) version of HornetQ.  The problem described in the other ticket persists. In addition, I get several new DEBUG level stack traces appearing in the log:

{noformat}
java.lang.Exception: null
        at org.hornetq.core.client.impl.ClientSessionFactoryImpl.<init>(ClientSessionFactoryImpl.java:181) ~[hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
        at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:737) ~[hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
        at hornet.samples.PingConsumer.main(PingConsumer.java:59) ~[classes/:na]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_29]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_29]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_29]
        at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_29]
        at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:291) ~[na:na]
        at java.lang.Thread.run(Thread.java:680) [na:1.6.0_29]
2012-12-04 13:06:51.692 DEBUG default    o.h.c.client.impl.ServerLocatorImpl - NodeUp ServerLocatorImpl [initialConnectors=[org-hornetq-core-remoting-impl-invm-InVMConnectorFactory], discoveryGroupConfiguration=null]::nodeID=9a11dc05-29e4-11e2-89b8-005056c00008, connectorPair=Pair[a=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory?server-id=0, b=null]
java.lang.Exception: trace
        at org.hornetq.core.client.impl.ServerLocatorImpl.notifyNodeUp(ServerLocatorImpl.java:1398) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
        at org.hornetq.core.client.impl.ClientSessionFactoryImpl$Channel0Handler$2.run(ClientSessionFactoryImpl.java:1529) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_29]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_29]
        at java.lang.Thread.run(Thread.java:680) [na:1.6.0_29]
2012-12-04 13:06:51.694 DEBUG default    o.hornetq.core.client.impl.Topology - Topology@15e0a283::NewMemeberAdd nodeId=9a11dc05-29e4-11e2-89b8-005056c00008 member = TopologyMember[connector=Pair[a=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory?server-id=0, b=null]]
java.lang.Exception: trace
        at org.hornetq.core.client.impl.Topology.updateMember(Topology.java:181) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
        at org.hornetq.core.client.impl.ServerLocatorImpl.notifyNodeUp(ServerLocatorImpl.java:1403) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
        at org.hornetq.core.client.impl.ClientSessionFactoryImpl$Channel0Handler$2.run(ClientSessionFactoryImpl.java:1529) [hornetq-core-2.2.21.Final.jar:2.2.21.SNAPSHOT (HQ_2_2_21_final, 122)]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_29]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_29]
        at java.lang.Thread.run(Thread.java:680) [na:1.6.0_29]
{noformat}
Are the innocuous? If not, what problem do they represent?

[clebert.suconic]

those are DEBUG statements.. with a trace...

I used them to debug issues when I was fixing issues, and decided to leave it there. Maybe they should be made trace instead of DEBUG level.

So they are innocuous.