At 2.2.5 you may have an exception being throwed at your client in case of a connection error (even though there's a thread still trying to reconnect).
Say, you tried this.
Producer.send(... some message...)
While the client is retrying to connect.
At 2.2.5 you will receive an exception and you will have to retry the operation. If you don't do a loop on this case your client will be finished accordingly to what you have programmed.
At 2.2.latest (on AS7 at the moment) it will block the send while the retry is being done.
It appears that no reconnection is happening, no matter how long I wait after restarting the server, no reconnect appears to happen. I want to try and trace this down more, but I can't seem to find a way to put the client into debug logging mode. My app uses log4j via commons logging, but setting log4j categories does not result in log output by the cleint. Is there any way for me to trace what the hornetq client code is doing when I restart my honretq instance?
Why don't you give a try at JBoss AS7? it's basically the same thing as the standalone.
OK, I finally figgured out my client side logging, and determned that the reconnect IS working after server restart - I suspect my original observations were based on a misconfigured server somehow.
I want to move our whole app to JBoss AS, but with a release looming, I gotta stick with standalone for now.
Thanks for the help.