Get Involved. Join the Conversation.


    M Sridhar
    Different Processors, Same Target Namespace
    Topic posted January 12, 2019 by M SridharSilver Medal: 2,000+ Points, tagged Cloud, Connection, ERP Cloud, Events, Integration, Mapping, Orchestration, PaaS, REST, Web Services, xml 
    72 Views, 9 Comments
    Different Processors, Same Target Namespace
    OIC Orchestration: Different Processors, Same Target Namespace

    I have integrations referring to multiple instances of same connection (ItemUpdateInvoke) in an Orchestration. 

    But most of integrations are getting activated successfully, some integrations are failing with ORABPEL-05215 

    XML parsing failed because "IllegalStateException


    -->  For failed orchestration, If we remove 2nd instance of ItemUpdate Connection, integration is getting activated successfully. So definitely issue is using same connection multiple times.


    Please let me know what could be the issue with some integrations can we fix




    • Hemanth Lakkaraju

      Most probably duplicate schema issue. You can look at .out log file and search with flow name, that will give you a hint of which schemas have conflict definition.

      Ideally, if you are referring to same service, you should not have this duplicate schema issue unless the service itself recognizes/references the elements differently.

    • M Sridhar

      Thanks..Yes, I can figure out by playing with iar file which could be duplicate schema....what is the fix for it if we have 2 instances of same connection..?

      • Hemanth Lakkaraju

        What do you mean by 2 instances of same connection - Two different invokes using same connection? or Two different invokes using different connections using same endpoint wsdl?

        If it is former - we need to figure out how the conflict is arising. Is it in the service itself or by the adapter - In any case, you can merge the schema conflicts in iar and re-import the flow. If it is latter - make sure both the connections are refreshed with latest metadata and a regeneration of invokes should fix the issue.

        • M Sridhar

          It is different Invokes using same connection... 

          I see application file and resource files are different for each can we merge it..?

          • Hemanth Lakkaraju

            You can't or shouldn't merge the files. You should merge the content of schema within the files, which is conflicting. Share the iar and the log file, I can take a look.

            • M Sridhar

              PFA iar file...Below is the error while activation...In the Orchestration, If I delete ProcessItemEFF Invoke, it is getting activated...Pls help

              composite: TESTCLSACT: ORABPEL-05215 Error while loading process. The process domain is encountering the following errors while loading the process "TESTCLSACT" (composite "oracleinternalics/TESTCLSACT!01.00.0000*cfb8d6f3-be1d-4cc8-9696-773e4609530a"): Error while creating process. error while attempting to instantiate the class for the process "oracleinternalics/TESTCLSACT!01.00.0000*cfb8d6f3-be1d-4cc8-9696-773e4609530a" (revision "TESTCLSACT"); the exception reported was: BPEL 1.1 compilation failed: TESTCLSACT(line 0): XML parsing failed because "IllegalStateException: XML element "{}anyType" of variable "ics_api_internal_ReadFilereadResponse" is not defined", Suggested Fix : n/a This error contained an exception thrown by the underlying process loader module. Verify the exception trace in the log (with logging level set to debug mode). . This error contained an exception thrown by the underlying process loader module. Check the exception trace in the log (with logging level set to debug mode). If there is a patch installed on the server, verify that the bpelcClasspath domain property includes the patch classes.

              • Hemanth Lakkaraju

                It is difficult to analyze without logs and identify with which invoke ProcessItemEff invoke is conflicting.

                It is different Invokes using same connection..

                As per your statement above, I tried to look at different invokes that the connection ProcessItemEff invoke is using in the iar and I don't see any conflicts.

                But I was able to see quite a few conflicts between the invokes - ProcessItemEff (Connection: PDHITEMUPDATEBIZINVOKE) and FindItem (Connection: PDHITEMFINDSERVICEINVOKE), which I can only confirm from the logs.