ConfigException in XI protocol handler

[Former Member]

Hi people,

We have a problem like this one almost once a day, see the error message we got

<i>com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler.

Failed to determine a receiver agreement for the given message.

Root cause: com.sap.aii.af.ra.ms.api.ConfigException:

Couldn't retrieve outbound binding for the given P/S/A values:

FP=;TP=;FS=EQ0_400;TS=SAE_NAS_QA;AN=ITF_I_S_LEGACY_CHARACTERISTIC_LIST;

ANS=http://soa.weg.net/70/mm/LegacyCharacteristicList/receiver</i>

Sometimes a full cache refresh solves the issue, sometimes is necessary to go to the adapter engine cache and delete it, sometimes both does not work. It is happening with only one integration scenario, SAP (Abap Proxy) -> XI -> Legacy (Soap).

Any help, please, let me know.

thanks!

roberti

[Former Member · Accepted solution]

SAP Note 1057990 solves your problem

Thanx

Aamir

[Former Member · Accepted solution]

Thanks Amir,

I checked this note and asked for basis team to check if those patches are applied. The error found on this note seems to be a little different of ours, based on <i>ConcurrentModificationException</i>, but we will certainly check it to.

thanks.

roberti.

[Former Member]

Hi Waldemar Roberti

this is error code 400 which stands for Bad Request

This code indicates that the server could not understand the client's request, or found it to be incorrect in some way.

for more details on error code follow the link

http://www.web-cache.com/Writings/http-status-codes.html

this you may also solve by restarting J2EE engine

steps to restart J2EE engine

1) run transaction SMICM

2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart

by this java engine will restart and will be up in 5-10 minutes and your problem will be solved

Thanks

sandeep sharma

PS ; if helpful kindly reward points

[Former Member]

Thanks sandeep,

It is not error code 400... EQ0_400 is the system name. The error is about not finding the outbound binding, but the entire message is correct. We found that restarting J2EE it come back working. Actually we are trying to find a way of solving the problem and don't stay restarting the server every day.

Thank you very much.

roberti

[Former Member]

Hi,

Sap aswered about this problem. It can be solved only with SP13 of PI 7.

Thanks for your help.

regards.

roberti