Solution : https://service.sap.com/sap/support/notes/1081722 (SAP Service marketplace login required)
Summary :
Terminations including CONNE_IMPORT_ILL_OBJECT_TYPE and CONNE_ILLEGAL_TRANSPORT_HEADER occur due to internal errors in the ABAP memory or SAP Paging, often as follow-ons from SAP kernel issues or host and OS problems. Such issues are challenging to reproduce, generally arising under high system loads or specific hosts. The resolution involves examining previous errors indicated by logs or dumps, addressing system resource bottlenecks, and for 64-bit systems, allocating SAP Paging in shared memory. Setting the profile parameter rdisp/PG_SHM equal to rdisp/PG_MAXFS avoids many potential errors by avoiding the use of a paging file.
Key words :
runtime error memory_get_block_free runtime error memory_get_block_address reason, runtime error conne_import_ill_object_type runtime error conne_illegal_transport_header, profile parameter rdisp/pg_maxfs, fatal errors previously occurred, profile parameter rdisp/pg_shm, runtime errors listed, oversized profile parameter, rdisp/pg_shm defines, check rdisp/pg_shm, unexpected process restart
Related Notes :
| 133909 | Maximum value for PG_MAXFS, PG_SHM, ROLL_MAXFS, ROLL_SHM |