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 03, 2016

Applies to:

Oracle SOA Suite - Version to [Release 11gR1]
Information in this document applies to any platform.


On : 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 

<!DOCTYPE lolz [ 
   <!ENTITY lol "lol"> 
   <!ENTITY lol2 "&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;"> 
   <!ENTITY lol3 
   <!ENTITY lol4 
   <!ENTITY lol5 
   <!ENTITY lol6 
   <!ENTITY lol7 
   <!ENTITY lol8 
   <!ENTITY lol9 

The wire message will fail with the following message ;

Error Code B2B-50083

Error Description Machine Info: ( Description: Document protocol identification error.
Error Severity ERROR
Error Text Document protocol identification error.


In the SOA logs ;


2014-010-18T16:52:48.742+00:00] [soa_server1] [ERROR] [] [oracle.soa.b2b.engine] [tid:$WorkWithListener@18f395a2] [userId: <anonymous>] [ecid: a256b0787d7e6bdd:1b771677:144b115c89b:-8000-0000000000267920,0] [APP: soa-infra] Error -:  B2B-50083:  Document protocol identification error.[[
Error -:  B2B-50083:  Document protocol identification error.
at oracle.tip.b2b.engine.Engine.identifyDocument(
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(
at oracle.tip.b2b.engine.Engine.processIncomingMessage(
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(
at oracle.tip.b2b.engine.Engine.handleMessageEvent(
at oracle.tip.b2b.engine.Engine.processEvents(
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms