DefaultMessageListenerContainer and exceptions

[bhl]

What's the right way to propagate a listener exception to the JMS provider using the DefaultMessageListenerContainer? Some of the resources used by my listener are unreliable and an exception thrown by one of them causes the DMLC to spam the app server's logs by continually trying and failing to handle the message. I'd prefer it just give up and let the JMS provider attempt a redelivery later, as happens when using an MDB.

-bl

[Juergen Hoeller]

Well, it's up to the JMS provider to redeliver the message to your DMLC. Configuring the JMS provider for appropriate retry limits and backoff delays is usually sufficient. Is there anything more specific that you would expect to happen within DMLC?

Juergen

[bhl]

My mistake. Looks like I configured one queue for redelivery and not the other.

-bl