Healthcare Adapter EndPoint Throwing Error While Parsing HL7 Message
(Doc ID 2200355.1)
Last updated on NOVEMBER 22, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.1.0 and laterInformation in this document applies to any platform.
Symptoms
Healthcare Adapter EndPoint throwing Error while parsing HL7 message
On Inbound HL7 DOD encoding message , the server end point throws the following exception:
Error -: HC-50083: Document protocol identification error.[[
at oracle.tip.b2b.engine.Engine.identifyDocument(Engine.java:5946)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2620)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1930)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4757)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:4205)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3772)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:784)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:246)
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:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:618)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)
at oracle.tip.b2b.engine.Engine.identifyDocument(Engine.java:5946)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2620)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1930)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4757)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:4205)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3772)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:784)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:246)
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:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:618)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)
STEPS
-----------------------
1) Send HL7 DOD encoded message to an inbound endpoint
2) The Exception " HC-50083: Document protocol identification error" is seen.
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 |