This is really nice hint, but I m sure there is no such thing occurring at the time of failure…
Hereby I searched the Wm Advantage Knowledge base and found the same issue for some other application….
Here is the issue and the solution from wm in bold
When executing the Trading Networks API
“wm.tn.profile:getInternalID” under heavy load conditions,
ebXML Module intermittently retrieves a “null” value for the internal ID.
The ebXML Module invokes the Trading Networks API
“wm.tn.profile:getInternalID” to fetch the internal ID
for a trading partner when processing an incoming message.
Under heavy load of incoming messages, this API may return
a “null” value for the internal ID. This behavior interrupts
the processing of the incoming message.
This issue is resolved. The internal ID for a trading partner
is now cached to avoid a fresh query to Trading Networks for
each incoming message.
WM has provided a fix to resolve this issue.
My question is now how can I get a fix for this issue? Shall I ask WM ??