qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin <Justin.Scad...@gd-ais.com>
Subject RE: 2 Client Question: Multiple Receivers & Aborting fetch()
Date Mon, 03 Feb 2014 16:13:14 GMT
Thank you very much. I had guessed that this was a bug, but I didn't want to make presumptions.
I'm glad it has been addressed, but is there any expectation on the release of 0.26?

From: Gordon Sim [via Qpid] [mailto:ml-node+s2158936n7603880h53@n2.nabble.com]
Sent: Monday, February 03, 2014 10:58 AM
To: Scaduto, Justin R.
Subject: Re: 2 Client Question: Multiple Receivers & Aborting fetch()

On 02/01/2014 12:13 AM, Justin wrote:
> 2. When my applications are destructing, if some thread has a fetch() call
> in progress with an infinite timeout, I cannot get that thread to end. My
> research seemed to show that calling close() on the session object should
> abort a fetch() call, but I am not seeing this work. Is there something else
> I should be doing or some other mechanism to force a fetch() call to return
> prematurely?

That is a bug that was fixed in 0.26:
https://issues.apache.org/jira/browse/QPID-4265

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]</user/SendEmail.jtp?type=node&node=7603880&i=0>
For additional commands, e-mail: [hidden email]</user/SendEmail.jtp?type=node&node=7603880&i=1>


________________________________
If you reply to this email, your message will be added to the discussion below:
http://qpid.2158936.n2.nabble.com/2-Client-Question-Multiple-Receivers-Aborting-fetch-tp7603800p7603880.html
To unsubscribe from 2 Client Question: Multiple Receivers & Aborting fetch(), click here<http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7603800&code=SnVzdGluLlNjYWR1dG9AZ2QtYWlzLmNvbXw3NjAzODAwfDE1ODM2NTAyNTQ=>.
NAML<http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>




--
View this message in context: http://qpid.2158936.n2.nabble.com/2-Client-Question-Multiple-Receivers-Aborting-fetch-tp7603800p7603882.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message