Queue Reconnection

I have a Receiver that is receiving messages from a Queue created in a Broker on another machine (Single delivery policy). If the connection goes down (i.e. I remove the network cable), I can detect the connection failure and then reconnect (once the cable is plugged in again). However the receiver cannot reconnect to the Queue for a while - it raises a Resource in Conflict exception.

I assume this is because the broker still thinks the original Receiver is connected, and eventually it does realise the connection was lost and allow the new connection to be establised.

Is there any way of configuring how long this takes? and, if its possible, what would be the impact of reducing the time taken to check that a connection is dead?

Thanks very much for your help.

[802 byte] By [MatthewHarrison] at [2007-11-25 8:37:07]
# 1

The broker identififes connections which are closed

when the connection was in a half open state (for example

connections closed during a network failure) by

periodically "pinging" inactive clients. This ping

allows the broker to identify those connections which

are now closed and reclaim the resources. In your case,

the queue receiver lock is released when the system

"pings" your client after the network is restored.

The default value is 2 minutes.

You can change how often the system checks by changing

the value of the property:

imq.ping.interval

in your default.property file

Guest at 2007-7-1 15:12:06 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 2
Excellent, thanks for your help
Matthew Harrison at 2007-7-1 15:12:06 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...