I'm using weblogic 10.3 on Solaris v10 and believe I may need to implement an error destination for my JMS queues.
I know how to do this but am not sure then how to go about dealing with any messages that are put into the error destination.
At a minimum I'd like to have some log output (in my webserver's log files) for each message in the error destination generated, identifying the properties of the message header.
Further I'd like to have the messages re-delivered to the queue from where they could not be delivered.
And further, have the messages deleted from the error destination if they cannot be delivered after a set number of resends to the originating queue.
I'd appreciate feedback as to wherher these items are achievable.
From my past JMS experiences I believe they are doable, however a whole lot of custom code would need to be written.
I'm hoping for a solution where Weblogic does most of the hard work form me.
I've posted this question as the extent of the documentation I've found out there regarding dead letters in Weblogic is to place a message into an error destination when it is deemed undeliverable. There seems to be verly little out there explaining how to handle dead messages in Weblogic 10.3 once they arrive in the error destination.
All help appreciated.