Calling open_sender will open a 'sender' link, and calling open_receiver will create a 'receiver' link. The two are mostly independent if you are simply sending to a queue, suggesting any difference being seen from adding the latter would probably be some interaction with the server configuration, other clients in use, etc. It seems likely your sender is either never being given any credit to send, or actually the messages are being sent but just not accepted (e.g instead released/modified/rejected) due to the particular setup. Or it could just be an issue in your program, or the client. Its hard to say much based on the limited info here.
On Fri, 11 Oct 2019 at 15:47, MattR <[email protected]> wrote: > > Hi All, > > I was hoping someone could explain the difference in what is going on behind > the scenes with Qpid Proton C++'s open_sender and open_receiver functions. I > am running into an issue with my class that is opening the sender and the > queue I am sending to not receiving messages. I have checked that when I > call the open_sender that a connection and channel (or "session" as I > understand it could be correlated with) are created, but no messages are > going through to the queue on send. When I qpid-stat I see that the queue > exists and it has consumers. However, if I add an open_receiver call > alongside my open_sender then the messages send just fine (qpid-stat > verifies this as well as on_tracker_accept is now getting called in my > code). Could someone explain what I might be missing or doing wrong so that > I do not require also calling open_receiver when I merely want to send > messages to my queue? > > All responses are greatly appreciated. > > - Matt R. > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
