You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by AF...@princeton.com on 2011/06/29 01:01:56 UTC
Call to Session::acknowledge not acknowledging messages
Under what conditions would a call to Session::acknowledge not acknowledge
the received message(s)?
As I mentioned earlier, I'm working on Python SWIG bindings, and my
receiver is unable to acknowledge messages. I don't think it's an issue
with the bindings, because I put so debug printing in
qpid::messaging::Session::acknowledge (both versions), and it is getting
called three times, once with the message, sync=false, then with no
message, sync=false and finally with no message, sync=true. Yet, there is
no message.accept in the wireshark traces.
Is there a suggested place I should put my examples, patches to the
bindings, and wireshark traces? (I would put the patches to the bindings
in bug tracker, but they need to be better organized first.)
--
Anthony Foglia
Princeton Consultants
(609) 987-8787 x233
Re: Call to Session::acknowledge not acknowledging messages
Posted by Pavel Moravec <pm...@redhat.com>.
Hi Anthony,
see AMQP (i.e. v 0.10) specification http://www.amqp.org/confluence/download/attachments/720900/amqp.0-10.pdf?version=1&modificationDate=1203467591000 and section 2.8 for some overview, and Class:tx starting on page 188 for technical details.
Kind regards,
Pavel
----- Original Message -----
From: AFoglia@princeton.com
To: users@qpid.apache.org
Sent: Wednesday, June 29, 2011 1:43:05 AM
Subject: Re: Call to Session::acknowledge not acknowledging messages
Nevermind. I believe I found my problem. I was making transactional
sessions.
I had never heard of transactional sessions before. Is there some simple
documentation on what they are somewhere?
--
Anthony Foglia
Princeton Consultants
(609) 987-8787 x233
<AF...@princeton.com> wrote on 06/28/2011 07:01:56 PM:
> Under what conditions would a call to Session::acknowledge not
acknowledge
> the received message(s)?
>
> As I mentioned earlier, I'm working on Python SWIG bindings, and my
> receiver is unable to acknowledge messages. I don't think it's an issue
> with the bindings, because I put so debug printing in
> qpid::messaging::Session::acknowledge (both versions), and it is getting
> called three times, once with the message, sync=false, then with no
> message, sync=false and finally with no message, sync=true. Yet, there
is
> no message.accept in the wireshark traces.
>
> Is there a suggested place I should put my examples, patches to the
> bindings, and wireshark traces? (I would put the patches to the
bindings
> in bug tracker, but they need to be better organized first.)
>
> --
> Anthony Foglia
> Princeton Consultants
> (609) 987-8787 x233
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Call to Session::acknowledge not acknowledging messages
Posted by AF...@princeton.com.
Nevermind. I believe I found my problem. I was making transactional
sessions.
I had never heard of transactional sessions before. Is there some simple
documentation on what they are somewhere?
--
Anthony Foglia
Princeton Consultants
(609) 987-8787 x233
<AF...@princeton.com> wrote on 06/28/2011 07:01:56 PM:
> Under what conditions would a call to Session::acknowledge not
acknowledge
> the received message(s)?
>
> As I mentioned earlier, I'm working on Python SWIG bindings, and my
> receiver is unable to acknowledge messages. I don't think it's an issue
> with the bindings, because I put so debug printing in
> qpid::messaging::Session::acknowledge (both versions), and it is getting
> called three times, once with the message, sync=false, then with no
> message, sync=false and finally with no message, sync=true. Yet, there
is
> no message.accept in the wireshark traces.
>
> Is there a suggested place I should put my examples, patches to the
> bindings, and wireshark traces? (I would put the patches to the
bindings
> in bug tracker, but they need to be better organized first.)
>
> --
> Anthony Foglia
> Princeton Consultants
> (609) 987-8787 x233