Basis Errors and Solutions

Restricting the display in the RWB performance monitor

July 7, 2009 at 1:27 am

[dim the display] [high performance] [monitoring] [OOM] [outofmemory] [performance] [performance bond] [runtime] [RWB] [Workbench]

Performance enhancements for Channel MonitoringSymptom Loading the channel data in Channel Monitoring takes a long time, especially when there are many channels configured for the Adapter Engine. Even using a more restrictive filter, that would include...
Performance problem in searching Person name on NAME_TEXTSymptom Performance problem in searching Person name on NAME_TEXT field. Other terms BAS_NAME, BAS_PERFORMANCE, ADDR_PERS_COMP_NAME_SEARCH, SO01 Reason and Prerequisites When the searching on the full name, a functionality introduced in the note...
Performance improvement for ‘Add’ Action in SynchronizationSymptom Middleware is taking a long time to send records for Add action during synchronization for any smartsync application. Other terms Smart Sync, Delta, Synchronization, Middleware, Application, Performance, Time, Data, Iteration, SyncBO,...
Performance issues when storing documents in SKWF layerSymptom You are trying to attach document using SKWF Framework. It takes large amount of time due to the check for duplicate entries in the SKWF Folder which already has large number...
Monitored Services do not appear in Monitoring Service/CCMSSymptom The Adapter Engine can report the backlog for XI Messages to the Java Monitoring service of the WebAS Java and from there to CCMS. The Monitoring is configured at Service level...
Message Overview: redirect to Message Monitoring failsSymptom You click on one of the counters in the Message Overview, that shows the number of Messages of a certain scenario and in a certain status. A new window opens that...
Message Editor: Editor loads the wrong payload versionSymptom If you start the Message Editor for an XI message for which an application error has occurred in the target system, the system then loads an incorrect version of the payload....
Manual cancelling of Messages triggers AlertSymptom You have configured XI Alerts in Runtime Workbench for your scenarios. Manual cancelling of XI Messages of the Adapter Engine in Message Monitoring triggers Alerts. Other terms RWB, Runtime Workbench Reason...

Symptom

You use the SAP NetWeaver Exchange Infrastructure and use performance monitoring in the Runtime Workbench. If you use a selection that leads to a very large result set, a memory bottleneck occurs in the Java stack.
Other terms

OutOfMemory, OOM, Runtime Workbench, RWB, performance monitoring
Reason and Prerequisites

You use the SAP NetWeaver Exchange Infrastructure and use performance monitoring in the Runtime Workbench (RWB) to display performance data for messages that have already been processed.
If you use a selection that leads to a very large result set (for example, if you select using a very large timeframe), a memory bottleneck occurs in the Java stack when the result set is displayed. In extreme cases, this may lead to an OutOfMemory error.
Solution

This note provides an option to define an upper limit for the size of the result set. The limit is defined in the ABAP stack by the program SXMS_RESTRICT_RWB_RESULT_SET. This upper limit ensures that, at most, the maximum entries for display in the RWB are transferred from the ABAP stack to the Java stack. If the size of the result set exceeds the upper limit, it is restricted to the most recent entries.
To implement this note, you mustfirstcreate the following blank report as an executable program without TOP include:
Title: SXMS_RESTRICT_RWB_RESULT_SET
Type: Executable program
Status: SAP Standard Production Program
Package: SXMS_PF_AGG
Implement the attached correction instructions or import the relevant Support Package.
Now create the following text symbols for the report SXMS_RESTRICT_RWB_RESULT_SET:
001 Restriction of result set
002 Maintain restriction
003 Status
004 Create restriction
005 Delete restriction
006 The result set is unrestricted
007 The result set is restricted
008 Maximum entries
009 Configuration not possible for this SP level
To run the report and display the restriction set, you require the following authorization:
Object: S_XMB_AUTH
Area: CONFIG
Activity: 03
To change the restriction set, you also require the following authorization:
Object: S_XMB_AUTH
Area: CONFIG
Activity: 02
Both authorizations are included in the following role by default:
SAP_XI_ADMINISTRATOR_ABAP.
At runtime, up to 24 megabytes are occupied in the Java stack memory for each 1000 line entries in the result set.
For the aggregated views (aggregated overview and aggregated detail data), the number of lines of the result set depends on the number of scenarios and the number of selected intervals. An upper limit is determined from
#configured scenarios*selected timeframe/interval lengths
For example: If there is a total of 20 configured scenarios, the highest number of lines when data from one week is displayed and there is a resolution of 15 minutes is:
20*168 hours/0.25 hours = 13,440
The upper limit is usually not reached because messages are generally not processed for all configured scenarios in the specified timeframe.
For the individual screens (individual overview and individual detail data), the number of lines of the result set corresponds to the number of messages processed in this timeframe.