activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jrosenberg@shopzilla.com (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1450) Timed failure notification for FailOverTransport
Date Tue, 13 Nov 2007 19:14:49 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40600
] 

jrosenberg@shopzilla.com commented on AMQ-1450:
-----------------------------------------------

Hi,

I'd be interested in your patch for this problem, it is something I'm wrestling with right
now.....

Also, have you tried using the TransportListener to detect failures, without breaking the
retry cycle?

Jason


Quoted from: 
http://www.nabble.com/-jira--Created%3A-%28AMQ-1450%29-Timed-failure-notification-for-FailOverTransport-tf4591250s2354.html#a13106640



> Timed failure notification for FailOverTransport 
> -------------------------------------------------
>
>                 Key: AMQ-1450
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1450
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>    Affects Versions: 4.1.1
>            Reporter: Diego Belfer
>
> It would be good to have a new property for the FailOverTransport, in order to define
the maximum time to wait when sending a message if a reconnection attempt is taking place.
> This would avoid blocking client threads for an unbounded amount of time, while it would
still allow an unbounded time for  the reconnection attempt.
> I was looking at the code, and it does not seem hard to add. I could add it if you think
it would be useful for others.
> Thanks,
> Diego Belfer

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message