SAP XI JDBC Communication Channels Not Polling or Hanging

If you see that a JDBC sender channel is not polling after a java node crash, check the locks.
When a JDBC sender channel polls, it sets a lock in the enqueue service (SCS instance).
With a crash, these locks will be left hanging and the channel will not poll until the lock is removed.

To get the channel to poll again, follow this process:

1. Stop the channel
2. Go to Visual Admin --> Locking Adapter --> Display locks tab and refesh the locks view.
3. Select the existing (hanging) enqueue lock with JDBC (The lock has $XIDBAD.JDBC2XI and channel ID in tis name.
The channel ID can be determined from <Path to server node>/log/services/com.sap.aii.adapter.jdbc.svc)
4. Delete the lock.
5. Start the channel

The problem can be avoided by setting 'taskTimeout' parameter in the channel.
When the channel sets a lock, it passes the value of this parameter to the enqueue service and the enqueue service will not hold this lock longer than this time.



If the channel is not polling after a connectivity problem (ex: the database server polled by the sender channel crashed and has come up later), check the scheduler.
You can call the scheduler URL http://<host>:<port>/AdapterFramework/scheduler/scheduler.jsp.
If you do not see the channel listed in the schedule, it is likely that there is a bug in the scheduler.

To get the channel to poll again deactivate and activate it. Check SAP note 1483974 to fix the bug.

If you find that the channel is hanging while connecting or executing SQL statement on an Oracle database, you need to deactivate and activate the channel. If there are message processed by receiver channel stuck in DLNG status, restart Messaging System service. To avoid the problem, you can set connection timeout driver:oracle.net.CONNECT_TIMEOUT or read time out driver:oracle.jdbc.ReadTimeout. Both the parameters are defined in ms.

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