Rafael H. Schloming commented on PROTON-512:

I would say it shouldn't necessarily do anything. Messenger is set up to create 
connections on demand, so if/when that connection is needed at some point in 
the future, e.g. the app tries to send another message, it will be recreated.

Where the question gets more interesting is for subscriptions and stored 
messages. Right now there is no attempt to re-deliver stored messages after the 
first attempt, and there is also no attempt to ensure that a live connection 
exists for subscriptions with positive credit. I wouldn't think of this as 
connection retry though since I don't think we ever want to blindly keep 
connections alive without cause. What is really being being retried is delivery 
of the message or issuing credit for the subscription. Now if a given route has 
no live connection when a message needs to be delivered, or if a given 
subscription has no live connection when credit is granted, then we should be 
able to create the necessary connection on demand.

> Possibility to set idle timeout for messenger
> ---------------------------------------------
>                 Key: PROTON-512
>                 URL: https://issues.apache.org/jira/browse/PROTON-512
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.6
>            Reporter: Tomas Soltys
>              Labels: features, patch
>             Fix For: 0.7
> I would like to specify an idle timeout for a messenger which would be then 
> used for all created connections. I see that there is an interface for 
> pn_transport_t which is allowing it but it is not accessible from outside.

This message was sent by Atlassian JIRA

Reply via email to