Skip to Content
0
Aug 03, 2016 at 07:43 AM

Eclipse RFC call killed the backend

47 Views

We have been using Eclipse for ABAP for some time.

We are used to seeing many RFC calls from eclipse.

But A few days ago we had a rogue RFC call, that took the system out for over an hour.

Runtime 1.5 hrs and memory consumed 4.6 gb. EM exhausted and heap too. PRIV mode.

Other people sessions began disconnecting and for 1.5 hrs the system was effectively unusable.

That really hurt.

Im hoping other eclipse users might know what caused this.

Can we prevent it happening again ?

VERSIONS.

Eclipse, all users on latest available version. Auto update.

ABAP Business Object Tools (Developer Edition) 1.41.1 ABAP Connectivity And Integration Development Tools (Developer Edition) 1.57.1 ABAP Core Development Tools (Developer Edition) 2.64.2 ABAP Development Tools for SAP HANA (Developer Edition) 2.64.1 ABAP Development Tools for Web Dynpro (Developer Edition) 1.57.1 BW CompositeProvider (Developer Edition) 1.14.3 BW DataStore Object (Developer Edition) 1.14.3 BW InfoObject (Developer Edition) 1.14.3 BW Open ODS View (Developer Edition) 1.14.3

SAP Backend

SAP_BASIS 740 0011 SAPKB74011 SAP_ABA 740 0011 SAPKA74011 SAP_GWFND 740 0011 SAPK-74011INSAPGWFND SAP_UI 740 0013 SAPK-74013INSAPUI PI_BASIS 740 0011 SAPK-74011INPIBASIS ST-PI 740 0003 SAPK-74003INSTPI SAP_BW 740 0011 SAPKW74011 MDG_FND 747 0009 SAPK-74709INMDGFND SAP_AP 700 0033 SAPKNA7033 SAP_BS_FND 747 0009 SAPK-74709INSAPBSFND WEBCUIF 747 0009 SAPK-74709INWEBCUIF

Attachments

stad1.png (36.6 kB)
stad2.png (10.6 kB)