How to Deal with Error: B2B-50025: Repository error: java.lang.RuntimeException: AppMessage is null
(Doc ID 2206017.1)
Last updated on DECEMBER 07, 2021
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11gR1 to 11g]
Information in this document applies to any platform.
The goal of this document is to provide some guidelines for dealing with B2B errors like: B2B-50025: Repository error: java.lang.RuntimeException: AppMessage is null
You may notice such errors in your B2B managed server log, and also associated with this, you may notice Application messages completed but no corresponding Business or Wire messages being created. From Business perspective, since there is no business message being created for associated Application message, we can say "the message is lost". It's not entirely true from the integration perspective, since the Application message is created in Oracle B2B, and it can be resubmitted and (maybe) this time processing can complete without hitting the race condition (and thus Business message will be created, along with the Wire message). But customers must have a mechanism for detecting these situations, where business message was not created.
The error in the log looks like this:
This issue is heavily noticed in the diagnostic log when at the same time a slow database performance is happening. We may conclude that a slow database performance is a key factor of increasing the number of these race conditions.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document