So, "technically" timeouts are supported for TCP Transports. Here are the URI configuration parameters: http://activemq.apache.org/tcp-transport-reference.html http://activemq.apache.org/tcp-transport-reference.html
And, if one uses the standard TCP URL of tcp://localhost:61616 and ActiveMQ is not running, one (correctly and immediately) gets a JMSException (caused by a ConnectionException) with the reason being that the connection is refused. However, in debugging, I noticed that if one uses the DEFAULT connection URL, these parameters are ignored and the default TCP URL of tcp://localhost:61616 is actually failover://tcp://localhost:61616. It's not obvious to me yet what the significance of the failover protocol actually means, but I'm still digging. icfantv wrote: > > Hi- > > Did a cursory search but didn't find anything related to this so I > apologize in advance if it's been asked and answered - I didn't see it. > > Is there a way to set a connection timeout on the connection factory class > such that the thread doesn't block until a connection is successfully > made? I see several timeout related methods in the connection object but > don't see anything specifically related to connection timeouts. > > Thanks in advance, > > --adam > -- View this message in context: http://www.nabble.com/Connection-creation-timeout-setting-tp21490199p21507617.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
