cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to find Channel ID

Former Member
0 Kudos

Hello All,

Ours is as XI 3.0 PRD env. XP0 , one of the execution of the message is getting failed showing the reason as "unable to find Channel ID " <CHANNEL_DETERMINATION_FAILED> .and this is an INBOUND scenario ....

This is the error description which got from audit log :

********************************

Sender Service :RP1 (R3 system )

Receiver Service :SITE_ELETROPAULO_PRD

Interface : urn:aes-com:crm_i_site_2via_lista_debitos MI_LISTA_DEBITOS

Error Category : XI_J2EE_ADAPTER_ENGINE

Error Code : CHANNEL_DETERMINATION_FAILED

Direction :INBOUND

Message Type : Recv

ERROR Description:

Error : Unable to find channel ID

Delivery of the message to the application using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Couldn't find delivery channel for message: 6deed200-e440-11dc-aa3a-0019bb29226a

*****************************************

this messages failed in yesterdays execution , and the same messages are executing success today with out any errors..

Can any one help me to find the root cause of the problem occured ...

Best Regards

Rakesh

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

This might be because of the cache update issue.... So u referesh your cache

Regards,

Abid

Former Member
0 Kudos

Hello All,

I am still facing the problem but found the root cuase of it & trying to fix the problem from application logic .

The first basic workaround should be whether cache is getting updated or not if not perform a full cache refresh and clear the SLD Cache data .

Even after doing that also and the configuation part is finely configured then we need to analyse from the application point of view as below (this is specific to our scenario which i am facing currently )

Concerned with our scenario it is failing due to :

1>Basically this execution is between SOAP <>XI <>RFC (website <>XI <>ERP ) ., as this is an synchronous execution it has both request phase & response phase .

2>In the first step at the request phase the user sends the request from website (SOAP) to XI and from XI to ERP back end system (R3 -->RFC) to collect the required data from the R3 system at RFC defined Function Module (Z_*) .

3>At this phase when XI doesnt get response at a stipulated time from R3 back end system due to R3 performance problems (high CPU Utilization,dialog response time ,network problems ...etc ) the message gets failed at Integration engine level showing the reason as "MessageExpired :Exception with its id No: ".

4>In our case this is happening due to high database load of R3 back end system and some of the DB level tables are being used frequently and to fix this from Basis end we need to see if any index could be added and from application end whether if any application logic need to be changed to reduce the load on the system and execute the function fastly with in the time .

5>And at the phase of the Response RFC <>XI <>SOAP , (R3 back end system <>XI <>website ) , when the requested data processed is taking much time and the XI returnsn the error at Adapter engine level as "Channel Id not found " under code "CHANNEL_ID_DETERMINATION_FOUND" ...

6>So if we see any phase (request & response ) the error is due to R3 back end system and its slow performance due to its performance issues .

7>And the same execution will get success also when the performance of the R3 back end system is fine (at non peak hours , and at week end too due to less load on the system .) .

8>This particular two error codes (MessageExpired & Channel_determination_found) is under the same Error Category "J2EE_ADAPTER_ENGINE" .This indicates the correlation between these two error types.

So after confirming the basic checks are fine (CPACache refresh, ID configuration of communication channel for that scenarios & load on XI system ) , you need to analyze towards the performance of the complete systems involved in that scenario from the reqestor and responser too.

Now we are trying to fix the problem from our back end performance issues by adding the additional index to DB level tables and adding few parameters too.Once it is fixed will update again .

Best Regards

Rakesh

Former Member
0 Kudos

Hi,

i am getting the error unable to find channel id in the adapter engine in case of synchronous SOAP Adapter

Though the message is successful in the integration engine, the adapter engine message fails with the error "unable to find channel id"

Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Couldn't find delivery channel for message

Could any one please let me know what is the cause of the error.

Thanks in advance,

Manohar.

nisarkhan_n
Active Contributor
0 Kudos

It might be mainly because of the cache update issue.

it is clear that it is not able the CC iD from the Pipleline steps becuase it might not have got updated from the ID.

I feel its a cache issue...did u check yestreday when you got this error the status of the cache contents in the RWB?

Former Member
0 Kudos

@ Sarvesh,

*******************

I have checked the Adapter Services in Visual Administrator and they all seems to be fine , and do you want me to check any thing more over there ?

******************

@Nishar,,

****************

what exactly you want me to check ? is it under Cache Monitoring tab of RWB ? or the Cache Notifications under Integration Directory ?

*****************

And this particular scenario is working properly today ....with out any changes made to it ...

Best Regards

Rakesh

nisarkhan_n
Active Contributor
0 Kudos

rakesh,

What i meant was when you get this error...goto to the RWB and check the Cache monitoring status...on the AE it might not be upadted....

i strongly feel that this error might be beacuse of the cache not getting updated from ID.

Former Member
0 Kudos

Hello Nisar,

Even after performing Full Cache Refresh (successfully completed) also the same error is comming up again ...And the log from the Integration Engine level (SXMB_MONI ) is :

***************************

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessageExpiredException: Message 1f000690-e8f1-11dc-a372-0019bb29226a(INBOUND) expired</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

***********************************

Can any one advise on this...

Best Regards

Rakesh Reddy

prateek
Active Contributor
0 Kudos

Which adapter r u using at receiver. If it is http, then make sure that u have used the correct port to post the data

Regards,

Prateek

Former Member
0 Kudos

Hi,

Though I am not very sure, but there could be a possiblity that, some of the services in Visula Admin went down.

Regards,

Sarvesh

Former Member
0 Kudos

Hi

it may be due to cache refresh..sometimes its happen whwn you execute any scenario some objects does not get updates so we will face this kind of problem..always try to do cache refresh for all the object after configuring whole scenario.

Kunaal

Former Member
0 Kudos

The above mentioned failed message is at Adapter engine level.

The same execution got failed at Integration level too and for that the error details from SXMB_MONI is :

****************************

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessageExpiredException: Message 39fd86e0-e408-11dc-8285-0019bb29226a(INBOUND) expired</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>