Interface Mapping weird behavour

[Former Member]

Hi everyone,

I recently transport an interface from qualification to Production environment.

This interface was working perfectly in Qualification but now, in Production I am experiencing some weird behaivors...

There is an interface mapping that changes a Source interface N1 to other source interface N2. In qualification everything is working well, but in Production I am getting an error. The error state :

<i>During the application mapping com/sap/xi/tf/_MM_XXXXXXX a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: Fatal Error: com.sap.engine.lib.xml.parser.Parser~</i>

and when i have a look at the sxmb_moni I can see that the message is received, but an error happen in the mapping.... and, the most weird of all, when I see the XML after the mapping, the <b>source message is N1 instead of N2?</b>

Has anybody has experienced the same problem any time?

has anybody any idea of what can be?

Thanks in advance.

Eduardo M.

[Former Member · Accepted solution]

Hi,

Just referesh your caches as mentioned in this document. This should resolve your issue:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a7930...

---Satish

[Former Member · Accepted solution]

Hi Satish,

Thank you for your quick answer.

I was thinking the same, in restart the Java side, because clearing the SLD cache nothing happen. But there are a lot operations in the production environment right now, and i will have to wait until the nigth to do it.

Anyway, this interface was transported two days ago, and NO CHANGES has been made in the production environment (there is not enable the edit of anything), so, it sounds a bit weird that the problem is in the cache (although it seems to be).

I will restart the java server in a couple of hours, but until this moment, has anyone any other idea?

Thanks!!!

[Former Member · Accepted solution]

I would rather suggest to reimport once again and refresh all the caches without any restart. It should resolve your issue. If not then the last option would be a restart.

---Satish

[Former Member · Accepted solution]

Hi Satish,

Finally refreshing the mapping cache was a sucess.

Thank you very much.

[agasthuri_doss]

Hi,

1) If you have used the Java Mapping, Kindly check out the class file you have imported is latest one.

2)Whethere you have used Content Conversion

If so check it,

This might help you

http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm

Regards

Agasthuri Doss