How WebSphere Application Server handles poison messages
From the developerWorks archives
Date archived: July 6, 2017 | First published: May 26, 2004
This article describes how poison JMS messages can be handled by the Embedded JMS Server provided with WebSphere® Application Server V5, how the default behaviour can be modified, and how the behaviour changes if WebSphere MQ is used as the message service provider.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.