How the Adapter rollback affects the ICEPAYLOADEXT status column (Doc ID 986452.1)

Last updated on DECEMBER 04, 2019

Applies to:

Goal

This document aims to solve the following concern:

In this particular scenario there is a LTMH adapter configured to send xml messages from the ICEPAYLOADEXT table to a queue. The following issues occur:
- A business exception was encountered. Rolling back.
- Exception: com.lodestarcorp.portal.PortalException
- Service is stopped for having too many errors

When monitoring the status in the ICEPAYLOADEXT table it is possible to see the states for the same message change from N (new) to P (processing) and back to N (new) again. That means that after the service is restarted the service will try to resend the message again (with the same result). The consequence is that the service is constantly restarting and trying to resend the specific message.

The question is the following: Why, when encountering rollback problems, the LTMH service doesn't leave the record in the ICEPAYLOADEXT in an error state (for instance E, J or EE)?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.