activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin C." <mart...@gmx.at>
Subject Re: ActiveMQ-CPP Failover transport blocks in interrupted mode
Date Fri, 12 Feb 2010 10:51:25 GMT


Martin C. wrote:
> 
> After this, the call to send() hangs, instead of timing out due to either
> connection.sendTimeout or timeout. This is rather unfortunate for me,
> because possibly "infinite" hangs are not what I want, but want to switch
> to some sort of "offline" handling.
> 
> Anybody got a hint for me?
> 

Ok, it seems I am missing a soConnectTimeout=3000000 on the tcp:// part of
the failover url.

With the following URL is acceptable for me.
url <<
  "failover://"
  <<(tcp://" << broker.ip << ":" << broker.port 
  << "?soKeepAlive=true&soConnectTimeout=3000000)?" 
  << "randomize=false"
  << "&connection.sendTimeout=5000"
  << "&maxReconnectDelay=5000&timeout=3000"

Best regards,
Martin
-- 
View this message in context: http://old.nabble.com/ActiveMQ-CPP-Failover-transport-blocks-in-interrupted-mode-tp27561136p27561784.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message