Cheers mate!!
Thanks Asankha.
Its working now :)

Thanks & Regards
Sunil Kumar Tiwari | I&B2B | Tech Mahindra Ltd. 
(Office: 009120 6641 7136  Mobile: 0091 9767644210)
Email: [email protected]


-----Original Message-----
From: Asankha Perera [mailto:[email protected]] On Behalf Of Asankha C. 
Perera
Sent: Wednesday, August 05, 2009 6:06 PM
To: [email protected]
Subject: Re: Synapse ESB and IBM MQ sender issue

Hi Sunil
> I am trying to read (enqueu) message from MQ queue and post(dequeue) it into 
> response MQ queue.
> Getting exception (PFA for exception) over Synapse ESB console for proxy 
> service when PS is trying to post (dequeue) message to MQ response queue.
>   
By default your configuration would read a message (along with all of
its transport level headers - i.e. JMS headers) and write them back as
read. However, some of the headers read (e.g. JMS_REDELIVERED) does not
seem writable with your JMS provider. With SYNAPSE-478 we fixed this to
work according to the JMS specs, but the header in question passes
through our filter.

Hence you could remove this header from the transport headers read
before the write like follows:

<inSequence>
  ...
  <property name="JMS_REDELIVERED" action="remove" scope="transport"/>
</inSequence>

cheers
asankha

[1] http://issues.apache.org/jira/browse/SYNAPSE-478 (See the last two
comments of this)

-- 
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com





============================================================================================================================

 
Disclaimer:

This message and the information contained herein is proprietary and 
confidential and subject to the Tech Mahindra policy statement, you may review 
the policy at <a 
href="http://www.techmahindra.com/Disclaimer.html";>http://www.techmahindra.com/Disclaimer.html</a>
 externally and <a 
href="http://tim.techmahindra.com/Disclaimer.html";>http://tim.techmahindra.com/Disclaimer.html</a>
 internally within Tech Mahindra.

============================================================================================================================

Reply via email to