error-channel on JMS adaptor

[rock_star]

Hi Mark/Oleg,

Can you please reply with your comments or suggest some alternate approach for this?

I really need to use the transact mode of ack.

Thanks

[plecesne]

Hi rock_star,

Indeed, using the error-handler will rollback the transaction anyway, but using the error-channel attribute will not (unless the channel is synchronous and the subscriber to this channel throws an exception).
We encountered your exact same case of looping indefinitely, and the error-channel feature solved it.

I also believe that the error-handler has a strange behaviour, as it does not "handle" the error, it's just a plain listener but it does not "catch" the error as its name makes it sound like.
However, the "error-channel" allows you to handle it just as you need (since SI 2.0 GA)

Hope this helps,

Pierre

[rock_star]

Hi Pierre,

Thanks for response. I am using error-channel as well and as you have pointed, the channel in my case is direct( synchronous).

I had pollable( asynch) channel but I removed that earlier as I did not want to use for reasons like:

1) Suppose someone pushed 1000 trades and by mistake the trade message format got in bad shape and that will result in error and that will make all these messages bad formatted messages end-up in error-channel attribute based channel.

And, if my system crashes at this point then I would loose all these messages as they were on pollable channel. Had this transacted thin handled in sync channel based on error-channel attribute, then this would have been avoided.

I know there is solution to back up the messages played by using message store, which somehow is not liked by team at the moment

-------------------------------------

As of now, I have switched to pollable channel error-channel attribute for testing but will try out some alternative.

Thanks a lot, Pierre.

[sunit singh]

hi all,

I have a problem i want to send all the message that result in an exception to a preconfigured queue , is there anything in the messagelistnercontainer to directly send such messages to an error queue.............as is the case in MDB , where after a configured number of retry mentoined in the ejb-jar.xml the message is sent to the system-error queue or any other configured error queue..!!!

regards and thanx