Positional Flat File Error After Upgrading from 12.1.3.0.0. to 12.2.1.4.0: B2B-50083 - Document protocol identification error
(Doc ID 2955461.1)
Last updated on JUNE 21, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
After upgrading from 12.1.3.0.0 to 12.2.1.4.0, inbound positional flat file processing fails with the following error.
ERROR
-----------------------
Error -: B2B-50083: Document protocol identification error.[[
at oracle.tip.b2b.engine.Engine.identifyDocument(Engine.java:6229)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2670)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1970)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4949)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:4379)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3913)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:944)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:258)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:184)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:633)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)
-----------------------
Error -: B2B-50083: Document protocol identification error.[[
at oracle.tip.b2b.engine.Engine.identifyDocument(Engine.java:6229)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2670)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1970)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4949)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:4379)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3913)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:944)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:258)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:184)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:633)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)
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 |