The MDB is not handling the CORRELATION_ID. I was under the impression that they would be treated as two separate operations. For example:
Operation One: HTTP request gets put on a queue by Synapse, and HTTP 202 returned to the client Outside of Synapse: MDB puts message on OUT_QUEUE (this simulates our normal backend processing) Operation Two: Synapse listens to OUT_QUEUE and makes HTTP request to specified endpoint, returning 202 to Synapse. -----Original Message----- From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 1:25 PM To: [email protected] Subject: Re: Switching transports - JMS to http using AQ Greg [EMAIL PROTECTED] wrote: > OK, that issue is fixed, but it's still not picking up the message from > the JMS queue. Just to let you know, here's my setup: > > I have two queues: MY_QUEUE and OUT_QUEUE. I enqueue a message on > MY_QUEUE by making an HTTP which synapse proxies to the JMS queue. > There's an MDB listening on MY_QUEUE, which picks up the messages and > enqueues it on OUT_QUEUE. The message still doesn't get picked up off > of OUT_QUEUE unless I restart Synapse. > > Does your custom MDB correctly handle the CORRELATION_ID? i.e. Synapse expects the response you place on the OUT_QUEUE to match the MESSAGE_ID of the request it placed on MY_QUEUE asankha This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
