wrong header metadata data during message processing

[Former Member]

Hi guys,

we have a scenario File => XI => Proxy where several Files are transfered to SAP Backend using the same proxy interface.

This scenarios is used for several systems of different countries. each country has it own diretory where the files are picked up.

Lately a following error occurs.

4 messages are sent for country A, 3 of them are processed correctly, but 1 has a corrupt main section during pipeline processing.

In the incoming message the correct sender service is used <SAP:Service>country_A</SAP:Service> but the processing

ends with the section CALL ADAPTER where the sender service is wrong <SAP:Service>country_B</SAP:Service>

This cause Problems at receiver side, because the data isn´t entered correctly

The processing of the 3 other messages ends with the step RESPONSE where the sender service is correct <SAP:Service>country_A</SAP:Service>

Has anybody an idea, why the sender service of one message is corrupt?

Kind regards

Jochen

[Former Member · Accepted solution]

Hi,

Can you check the receiver determination for your file sender.

Regards,

sreenivas.

[Former Member · Accepted solution]

Hi sreenivas,

thanks for helping.

for all 4 messages there is only one receiver determination.

successfull messages have following pipeline steps in sxmb_moni:

inbound message, Receiver Grouping, Response

the corrupt message has follwing steps

inbound message, Receiver Grouping, Call Adapter

In all steps but the last there is the same data in the Soap Header/Main Section.

but the last one is different.

Kind regards

[Former Member · Accepted solution]

Hello,

Are these 4 files are similar or is there any difference for the 4 th file...

And have you done any conditional routing in reciever determination...

Can you check you file adapter for the 4th file....in RWB

Let me know

Regards,

Sreeni.

[Former Member · Accepted solution]

Hi,

I checked the everything you said.

there is no conditional routing,the files are all of the same kind and the log in RWB looks the same for all 4 messages.

I tested this 4 files at our quality XI and all of them have been processed successfully without courrupt sender service.

Afterwards I compared the configuration of Q and P XI system and everything looks the same.

what could be the cause for other sender service?

why do this message end up in the step Call Adapter when all the others end up in step Response?

Kind regards

Jochen

[Former Member · Accepted solution]

Hi,

Can you do cache refresh...

Transaction: SXI_CACHE...Delta and Full refresh

and CPACache full refresh

http://<server:port>/CPACache/refresh?mode=full

Regards,

Sreenivas

[Former Member · Accepted solution]

Hi,

I made a cache refresh.

Unfortunately I have to wait until next message is to be sent, to check if this

was the cause of the failure.

thanks for helping

Kind regards

Jochen

[Former Member · Accepted solution]

Hi,

It seems that the cash refresh solves this issue.

Now the messages are processed correctly.

Thank you very much for your help.

Kind regard

Jochen

[Former Member · Accepted solution]

Hi guys,

this issue appears from time to time.

What could be the reason for such a behaviour.

Are there general cache problems and how to check these?

Kind regards

Jochen