RFC CallReceive error <Function BAPI_TRANSACTION_COMMIT:RFC_COMMUNICATION_FAILURE-
ERROR no conversation found with id 62629624
TIME Mon Dec 3 16:28:41 201
RELEASE 711
COMPONENT CPIC (TCP/IP) with Unicode
VERSION 3
RC 473
MODULE r3cpic_mt.c
LINE 9186
COUNTER 1
Hmmm not in an automated way that I know of (did not look in to that either though).
Check tx sm37 for the particular BODS background job. If there is a delay and the delay is longer than the foreground time-out session, then there is your cause.
And you can check in the BODS log. Normally it shows something like:
When the job is staying on the second line for a long time, then BODS is waiting for the job to be started. When that takes too long, the foreground connection that BODS uses to poll the status of the job gets timed out.
When the 3th line occurs then the background job is started and BODS keeps the connection alive because it polls once in a while the status.
It is a design fault that BODS lets the connection time out when the background job is delayed and is present for ages.
And worse: BODS cannot recover at this point. So the background job is scheduled and will start to run some time. If you restart your BODS job you can end up with multiple background jobs running at the same time wasting resources and possibly corrupting your .dat output file.
This error occurs not only on an ABAP dataflow but also in extractor jobs…when I look ODQMON for that, then it was errored…but then for extractor loads there are no background jobs on the SAP side…
Which extractor is that? I’ve seen some really problems with some of the CRM extractors - they are either hideously slow or just time-out. It does appear that while the DS extractor calls time-out, the BW ones do not time-out but take very long to process as well.
Avoiding the CRM extractors and using R/3 (ABAP) DFs and/or RFC Streams seem to have worked better for us.
Did you get the solution, if yes can you please share as I am also facing the same issue while extracting with crm extractors.
Regards,
Tilak
[/quote]
Tilak, our extractor issues are gone when SAP assessed the SAP Landscape’s performance and increased the number of process servers. After then, and until now, we had no big issues posted. Also as possible use the Extractors in Query Mode than importing them in CDC mode. CDC mode is really meant when you either use a delta process or if you will have to use the extractors with some filters.
We had someone who by default had imported all the Extractors in CDC mode which created a huge list of issues.
(BOB member since 2008-07-17)
(BOB member since 2012-03-20)
(BOB member since 2012-03-20)
(BOB member since 2007-01-10)