JDBC Receiver Channel: 'Maximum Concurrency' and 'poolWaitingTime'

The receiver communication channel uses 'Maximum Concurrency' and 'poolWaitingTime' parameters while negotiating a JDBC connection to a database. The default values of this parameters are 1 and 5000 ms respectively.


Maximum Concurrency is the number of parallel database connections that receiver channel can open and poolWaitingTime is the amount of time, in ms, the channel waits for a free connection when all the parallel connections are being used.

When Maximum concurrency is set to 1, poolWaitingTime should be set to 0. This makes sure the channel can wait infinitely to get the DB connection. This will prevent messages to get into error state with error similar to this:

Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has reached maximum concurrency (5,000 concurrent messages) and no free resource found within 5,000 milliseconds; increase the maximum concurrency level.

When maximum concurrency is set to > 1 poolWaitingTime should be set to an optimum value. Setting maximum concurrency to a very large number can affect other JDBC receiver channels. Check this linked post to prevent a receiver channel from being a bottleneck to other channels.

Setting poolWaitingTime Parameter:

To set poolWaitingTime, enable the 'Advanced Mode' option in 'Additional Parameters' tab and add the parameter poolWaitingTime with an appropriate value.



In case the JDBC communication channels are not polling at all, check this post out: http://www.sapnwnewbie.com/2011/05/sap-xi-jdbc-communication-channels-not.html

Thanks for reading. Please consider sharing it in your network of friends if you think this will help them.

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