Oracle B2B Is Not Handling The Xml Of Type Which Has An In-line Entity Defined For Rosettanet
(Doc ID 1940842.1)
Last updated on NOVEMBER 13, 2023
Applies to:
Oracle SOA Suite - Version 11.1.1.4.0 to 11.1.1.7.0 [Release 11gR1]Information in this document applies to any platform.
Symptoms
On : 11.1.1.4.0 version, Core B2B Platform
Oracle B2B is not able to process an inbound XML message which which is using 'in-line' XMLschema references, for example ;
<!DOCTYPE Pip3A4PurchaseOrderConfirmation SYSTEM
"3A4_MS_V02_03A_PurchaseOrderConfirmation.dtd">
<!DOCTYPE lolz [
<!ENTITY lol "lol">
<!ENTITY lol2 "&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;">
<!ENTITY lol3
"&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;">
<!ENTITY lol4
"&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;">
<!ENTITY lol5
"&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;">
<!ENTITY lol6
"&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;">
<!ENTITY lol7
"&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;">
<!ENTITY lol8
"&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;">
<!ENTITY lol9
"&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;">
]>
<Pip3A4PurchaseOrderConfirmation
xmlns="http://www.comstor.co.uk/b2b/BT/PIP3A4/PurchaseOrderConfirmation">
The wire message will fail with the following message ;
Error Code B2B-50083
Error Description Machine Info: (soa.vm.oracle.com) Description: Document protocol identification error.
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Document protocol identification error.
In the SOA logs ;
2014-010-18T16:52:48.742+00:00] [<SERVER>] [ERROR] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@18f395a2] [userId: <anonymous>] [ecid: <ECID>] [APP: soa-infra] Error -: B2B-50083: Document protocol identification error.[[
Error -: B2B-50083: Document protocol identification error.
at oracle.tip.b2b.engine.Engine.identifyDocument(Engine.java:5211)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2342)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1766)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4181)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3857)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3330)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:610)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:192)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
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 |