Reducing the chances of OutofMemoryError in SAP XI

If you have restrictions on the maximum heap memory that can be allocated for J2EE engine, chances of OOM error can be reduced by reducing maximum message size and messages/mappings that can be processed in parallel. Following are few suggestions:

1. Reduce the number of parallel mappings.

Reduce "Number of Connections" for the destination AI_RUNTIME_JCOSERVER in JCo RFC Provider service.
This will reduce the maximum number of simultaneous mapping requests that can be made, reducing memory consumption.

2. Reduce the number of threads allocated for each adapter.

By reducing the number of threads allocated for each adapter, the number of messages that are processed in parallel can be reduced. You can control the thread allocation for each adapter by customizing messaging.connectionDefinition property in the service SAP XI AF Core.
 
Check http://sapnwnewbie.blogspot.com/2010/10/threads-per-adapter-type-and-receiver.html

3. Reduce the time interval within which the synchronous messages are deleted.

If you have a large synchronous message traffic, increase the frequency at which the synchronous messages are removed from memory. The default is one day. Reduce the time interval by changing messaging.syncMessageRemover.checkInterval in SAP XI AF Messaging service.

4. Set limit on the maximum size of the file that can be picked by File Sender.

The File Sender channel can be made to error out if it has polled a large file. Limit on the maximum size of the file that can be picked by File Sender can be set by adding "Maximum File Size" property in Advanced Mode. If a large file is polled, the channel will error out. The channel may be erconfigured to pick the large file during low load times to avoid OOM error.

5. Set limit on the maximum message size on JDBC Sender channel.

The JDBC Sender channel can be made to error out if it has fetched a large amount of data. A limit on message size can be set by adding the following parameters in Advanced Mode:

msgLimit        true/false
maxMsgSize        Message size in KB
maxRowSize        Size of a row in KB
msgLimitErrorInterval    Time (in seconds) the CC will wait for next poll following the error

Check SAP Notes 1296819 and 1253826 for more details.


Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more