Quantcast
Channel: SCN : Unanswered Discussions - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 6719

Serialization issue with Message Split using maintain order at runtime.

$
0
0

Hi Folks

I am facing below issue.Can anyone help.

 

My Scenario

Proxy to SOAP (multiple receiver)

 

I have a proxy message which goes to 2 different system Suppose System1 and System2.

System1 is a direct call, no issue with it.

But when it comes for System2, based on values in payload the message can be split into multiple message.

for example: payload can be for Add, Delete or Update. We have 3 separate mapping. One payload can have all togeather as well.

But on target side they expect message in sequence. Add should come first then Update.....

 

For this i added "maintain order at runtime" and i get this below error.

All messages get stuck in ECC smq2 with this error.

 

If i remove maintain order at runtime, it works fine without issue but it wont be in sequence.

 

com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not assign next EOIO sequence number for SC: XI_OUTBOUND_XI_SERIALIZE4914__XXXXX. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Multiple EOIO contexts cannot be used within one transaction. Previous: XI_OUTBOUND_XI_SERIALIZE9407__XXXXX Current: XI_OUTBOUND_XI_SERIALIZE4914__XXXXX at


Below is my configuration


12.jpg


Viewing all articles
Browse latest Browse all 6719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>