1841081 - Performance issue caused by shared memory limitation | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

1841081 - Performance issue caused by shared memory limitation

Symptom

  • Java application is responding very slow. For example, navigation or open PDF take very long time.
  • In defaultTrace file, following information output:

[...]
The predefined size of the shared memory monitoring slots for the thread system is reached: size[600], used[600], type[thread table]. Every thread started from now on will be fully functional but will not be visible
 in the MMC thread monitoring. You need to reconfigure the shared memory monitoring slots for threads.#
[...]


Read more...

Environment

  • SAP NetWeaver 7.3
  • SAP enhancement package 1 for SAP NetWeaver 7.3
  • SAP NetWeaver 7.4
  • SAP NetWeaver Composition Environment 7.1
  • SAP enhancement package 1 for SAP NetWeaver Composition Environment 7.1
  • SAP NetWeaver Composition Environment 7.2

Product

SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP NetWeaver Composition Environment 7.1 ; SAP NetWeaver Composition Environment 7.2 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 1 for SAP NetWeaver Composition Environment 7.1

Keywords

Performance, Shared memory, AS JAVA J2EE server, monitoring slots , KBA , SV-PERF-JAS , Performance Incidents related to NW AS Java , BC-JAS-SF , Startup Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.