Whether you need to set this or not depends on what you're trying to achieve, and I'm not sure what that is.....

I am facing this exact same problem. Statement in User Manual is confusing. So is the Example.

All I want is my clients to re-attach (without triggering ExceptionListeners) to server on transient network failures (e.g. some delay in response, ping pong/packet loss etc ). What are the changes I need to make in JMS configurations. Appreciate your help on this.

Any advice on this?

Bijith Kumar wrote:

 

Any advice on this?

What Josh Britton said is correct.

The default value is -1, i.e. no automatic reconnection.

The statement in the user manual that it's 1 MiB is a typo, this has already been discussed on other threads.

Thank you Tim for the clarification. I have another question though. If the deafult value for confirmation-window-size is -1 (means re-attachment disabled), then how does the reattach-node example work with this default value. I don't seee this example change deafult value anywhere (neither using API nor in hornetq-jms.xml)

If it can't reattach it will try reconnecting.

For the difference between reconnection and reattachment see this chapter:

http://hornetq.sourceforge.net/docs/hornetq-2.0.0.GA/user-manual/en/html/client-reconnection.html

I understand teh difference. However, the purpose of re-attach example is to demonstrate re-attach and not reconnect. Below statement is from the description of re-attach example

When the client reattaches to the server it will be able to resume  using its sessions and connections      where it left off

This is different to client reconnect as the sessions, consumers  etc still exist on the server. With reconnect      The client recreates its sessions and consumers as needed.

So it seems the example is wrong.  i.e. it should have changed the confirmation-window-size from default -1. This caused the confusion.

Looks like the example wasn't updated when the confirmation-window-size default was changed from 1 MiB to -1