On Wed, Nov 4, 2009 at 4:28 PM, Schneider Christian <[email protected]> wrote: > Hi Claus, > > of course brokers like ActiveMQ have a great dead letter facility. > Unfortunately we are stuck with Tibco EMS here. > As it seems EMS by default will discard messages after the maximum number of > redeliveries. > You can set a property JMS_TIBCO_PRESERVE_UNDELIVERED=true to make Tibco > delivery the message to the dead letter queue after the retries. The problem > is that this property has to be set on each message by the client. >
We fixed an issue on trunk with JMS_<vendor> headers. But if you have to set them on the client then you are kind lost as I assume Camel is the one that consumes from the JMS queue. And I doubt you can set the header *afterwards*. I would ask the TIBCO people if there isnt a better way. Some FUSE customers do also have Tibco and I havent header of this issue before. > Can I set this property with Camel? I searched a little in the documentation > and the code and it seems that properties that start with JMS but are no > official headers are ignored. > > So as this is a little difficult to do in Tibco EMS I was thinking about > using the dead letter or onException facitlity in camel instead. > Yeah you can do that as a plan b. > Greetings > > Christian > > > > Christian Schneider > Team Handel und Risikomanagement > Informationsverarbeitung Business Solutions Trading > EnBW Systeme Infrastruktur Support GmbH > > Informationsverarbeitung > Business Solutions > Handel und Dispatching > Durlacher Allee 93 > 76131 Karlsruhe > > Tel : +49-(0)721-63-15482 > Mail: [email protected] > > Sitz der Gesellschaft: Karlsruhe > Handelsregister: Amtsgericht Mannheim HRB 108550 > Vorsitzender des Aufsichtsrats: Dr. Bernhard Beck > Geschäftsführer: Jochen Adenau, Dr. Peter Krampf > > -----Ursprüngliche Nachricht----- > Von: Claus Ibsen [mailto:[email protected]] > Gesendet: Mittwoch, 4. November 2009 15:04 > An: [email protected] > Betreff: Re: AW: AW: AW: Problem with SOAP/JMS and transactions > > On Wed, Nov 4, 2009 at 2:56 PM, Schneider Christian > <[email protected]> wrote: >> Hi Willem, >> >> that is fine with me. I have closed the ticket. >> >> I have another exception problem though. I want to define a rule for the >> other exceptions that should not return a fault. I want these exceptions > to >> be forwarded into something like a dead letter queue after some retries. >> >> I see two different ways to achieve this. >> >> 1) I could simply let them be rolled back and then use a filter for the > jms >> header JMSXDeliveryCount>n. So I could route any message that is > redelivered >> for the n´th time to a dead letter queue. >> > > The JMS Broker have a build in dead letter queue mechanism. > > > > -- > Claus Ibsen > Apache Camel Committer > > Author of Camel in Action: http://www.manning.com/ibsen/ > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
