On 20 January 2017 at 19:06, Gordon Sim <g...@redhat.com> wrote: > On 20/01/17 18:40, Rabih M wrote: >> >> I inserted the map directly into the ObjectMessage like you told me >> Robbie and it worked. >> >> But like the proton-j case, the connector is not being created on the >> Qpid-dispatch side. >> I attached the amqp communication into this mail. > > > The last frame in that file is incomplete (the previous error regarding the > map body may or may not be a wireshark issue),but that last frame is likely > the response which would indicate the success or otherwise of the frame. Is > there anything logged by the router? > > If you can, just running the router with PN_TRACE_FRM=1 is simpler for this > sort of thing in my view. >
As Gordon suggests, the proton trace logs might be more helpful. You can also do that with proton-j, and this the JMS client too since it uses proton-j. One key difference from the qdmanage case is you are not setting a reply-to value or correlation-id to use along with it. I don't know if the router cares about not being able to send a response or not though, but it might. Robbie --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
