Clarification on client-reconnect in non-HA standalone HornetQ 2.2.5

[wblackburn4]

I have a single instance of standalone HornetQ serving several JMS clients. I use the local JNDI server to configure connection fatories and retrieve them during startup. The clients create a connection and a session, keeping both open and using javax.jms.MessageListener implementations to consume messages. Connections have these attributes:

<retry-interval>1000</retry-interval>

<retry-interval-multiplier>1.5</retry-interval-multiplier>

<max-retry-interval>60000</max-retry-interval>

<reconnect-attempts>1000</reconnect-attempts>

If I restart HornetQ, my clients do not reconnect - I assume I am doing something wrong, but as I study the documentation I seem to see a contradiction, specifically:

"Alternatively, the server might have actually been restarted after crashing or being stopped. In this case any sessions will no longer be existent on the server and it won't be possible to 100% transparently re-attach to them.

"In this case, HornetQ will automatically reconnect the connection and recreate any sessions and consumers on the server corresponding to the sessions and consumers on the client. This process is exactly the same as what happens during failover onto a backup server."

This seems to imply that reconnection should be automatic. But if I read further on, I see:

"If your client does manage to reconnect but the session is no longer available on the server, for instance if the server has been restarted or it has timed out, then the client won't be able to re-attach, and any ExceptionListener or FailureListener instances registered on the connection or session will be called."

Which seems to imply that I must manually code such reconnection logic.

Can you please clarify what I should expect HoretQ to handle automatically, and what I must code into application logic?

Thank you.

[clebert.suconic]

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.

[wblackburn4]

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?

[clebert.suconic]

Why don't you give a try at JBoss AS7? it's basically the same thing as the standalone.

[wblackburn4]

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.