Skip to Content
0
Former Member
Apr 07, 2015 at 01:58 PM

Connection closed (no data) while calling RFC

6174 Views

Hi Experts,

We are facing multiple Runtime Error with short text as "connection closed (no data)" while calling a RFC.

Is it due to some connection link downtime or other issue ? I have provided the details of the dump in the following section.

If any more details needs to provided then i can provide the same.

Waiting for your valuable feedback. Thanks in advance.

system environment


SAP Release..... 740
SAP Basis level 0004

Application server... tdclxsrv203
Network address...... 10.11.175.23
Operating system... Linux
Release.............. 3.0.93-0.5-default
Hardware type....... x86_64
Character length..... 16 Bits
Pointer length........ 64 Bits
Work process number... 32
Shortdump setting. full

Database server... tdclxsrv201
Database type..... ORACLE
Database name..... PU6
Database user ID SAPISU

Terminal.......... 10.11.175.36

Character set C

SAP kernel....... 741
Created on....... Oct 6 2014 00:06:41
Created at....... Linux GNU SLES-11 x86_64 cc4.3.4 use-pr1
Database version OCI_112, 11.2.0.3.0, V1, default
Patch level....... 100
Patch text.......

Database............. ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*
SAP database version. 741
Operating system... Linux 2.6, Linux 3

Memory consumption
Roll.... 0
EM...... 8177304
Heap.... 0
Page.... 16384
MM used. 7649840
MM free. 523624

User and Transaction
Client................. 100
User.................. WF-BATCH
Language key.......... E
Transaction.........
Transaction ID...... 552229411B9E081CE10000000A0BAF17

EPP whole context ID...... 0050569C6EF81ED4B78FE13E8EA8325F
EPP connection ID........ 552229431B9E081CE10000000A0BAF17
EPP call counter......... 32

Program.............. ZSRR_PRO
Screen.............. SAPMSSY1 3004
Screen line.......... 2
Active debugger..... "none"

Server-Side Connection Information
Information on caller of Remote Function Call (RFC):
System.............. PU6
Installation number 0020284189
Database Release..... 740
Kernel Release...... 741
Connection type..... 3 (2=R/2, 3=ABAP-System, E=External,
R=Reg.External) call type....... synchronous and transactional type T (emode
0, imode 0)
Inbound TID..........
Inbound Queue Name...
Outbound TID.........0A0BAF17081C5522BCB30164
Outbound Queue Name..

Client................. 100
User.................. WF-BATCH
Transaction.........
Call program............SAPLERFC
Function module..... ARFC_DEST_SHIP
Call destination..... WORKFLOW_LOCAL_DEADLINE_100
Source server...... tdclxsrv203_PU6_10
Source IP address.. 10.11.175.23

Additional information on RFC logon:
Trusted relationship..
Logon return code.... 0
Trusted return code.. 0

Comment:
- In all releases prior to 4.0, no information is provided about the
caller.
- The installation number is provided in caller Release 700 and higher.
Additional information on RFC logon:
Trusted relationship..
Logon return code.... 0
Trusted return code.. 0

Comment: In Releases < 4.0, information about the RFC caller might be
missing or incomplete.

Information on where terminated
The termination occurred in ABAP program "ZSR**", in
"ZGETPRE**". The main program
was "SAPMSSY1".

In the source code, the termination point is in line 319 of (Include)
program "ZSR**".