cancel
Showing results for 
Search instead for 
Did you mean: 

parallel processing -> CALL_FUNCTION_SEND_ERROR

michal_hrncirik
Explorer
0 Kudos

hi gurus,

i have implemented parallel rfc call in my main rfc-function module ( FuBa_1 ).

The main rfc-function module gets up to 250 data sets in 1 request.

These data sets are processed by another function module( FuBa_2 ). in parallel with the restriction that max. 3 parallel calls at once are allowed.

The FuBa_1 gets the request 3 times in 4 minutes.

There was requirement that this FuBa_1 cannot run longer then 20 seconds.

I have implemeted a timeout.

The run of the FuBa_1 is terminated when

1. all results of parallel processing has been received ( number of sent tasks EQ number of received tasks )

2. timeout has been reached

the problem is that 1 or 2 times in hour comes the short dump CALL_FUNCTION_SEND_ERROR

An error occurred when executing a Remote Function Call.

"CPIC-CALL: 'ThCMSEND' : cmRc=18 thRc=0#Statistik nicht aktiv "

Status of connection.... "CODE=CM_DEALLOCATED_NORMAL CM_SEND_RECEIVED

CM_COMPLETE_DATA_RECEIVED SAPCODE=0 CONV=49357134"

Internal error code.... "RFC_IO5"

There is an error in the communication system. To clarify

and resolve the error, contact your system administrator.

FuBa_1 and FuBa_2 are in the same SAP system.

Any idea what can be the cause of this short dump?

thank you!

regards,

michal

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

I've seen this same error a couple times in my parallel processing but it was because the spun off process timed out or otherwise abended. The main program lost communication with the RFC and threw this error. If you are on a multiple app server environment, perhaps is has something to do with this thread running on another app server and abending?

You might post the code on how your calling the RFCs...that might help in a diagnosis.

michal_hrncirik
Explorer
0 Kudos

hi, Thank You for Your post.

Is there any standard functionality in place to kill the running child processes when the mother process reachs the timeout?