I think that is not what i mean. I have a situation at testing activemq
performance, where on a longer time period nothing happens at a connection.
And so an Exception occurrs and i cant send other messages. I set
wireFormat.maxInactivityDuration=0 to change that.
If i understand it correctly the failover only works if i set the
failover connection, and not in that way to connect to the same uri.
James Strachan schrieb:
Its called failover the URI to use btw...
http://activemq.apache.org/how-do-i-configure-automatic-reconnection.html
On 28/01/2008, Rob Davies <[EMAIL PROTECTED]> wrote:
On Jan 27, 2008, at 9:28 PM, Marco Buss wrote:
Rob Davies schrieb:
On Jan 27, 2008, at 12:22 AM, tpamsler wrote:
Marco,
Thank you for the response. Are there limitations on how long a
session can
stay open and the number of messages it can handle? If I use the
2nd example
in our application, the session may stay open for a few weeks.
Best,
-- Thomas
Marco Buss wrote:
You only need one session for your Messages. So your 2nd example
is ok.
--View this message in context:
http://www.nabble.com/Using-one-session-per-message-tp15114117s2354p15114519.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
There is no limit to how long a session is open - so weeks will be
ok ;)
cheers,
Rob
And what happens if the connection fails (timeout on tcp)?
If you use the reliable transport you get automatic reconnection - see
http://activemq.apache.org/uri-protocols.html
This includes getting a replay of the clients state - so from the
developers point of view, a failure/reconnect is seamless.
cheers,
Rob
