Inbound 997 Messages Stuck In B2B 12.2.1.3.0
(Doc ID 2534532.1)
Last updated on AUGUST 16, 2024
Applies to:
Oracle SOA Suite - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.3.0 version, B2B Engine
B2B inbound 997 from a partner gets stuck in Wire message level.
the following error occurs.
ERROR
-----------------------
[2019-04-03T12:22:48.400+00:00] [SOA] [NOTIFICATION] [] [oracle.soa.b2b.engine] [tid: DaemonWorkThread: '30' of WorkManager: 'wm/SOAWorkManager'] [userId: ] [ecid: ,0] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] [FlowId: ] FunctionalAck:: processIncomingMessage: Lock Time out while locking bizmsg for FA processing.Sleeping 100 ms and then retry
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |