IY73035: "FORCE APPLICATION" ON GATEWAY CAN CAUSE GATEWAY INSTANCE CRASH IF MONITOR IS TURNED ON GATEWAY

Error description

User affected: Users who use V8 client ->V8 Gateway ->DB2 server configuration.

Problem description:
In V8 client -> V8 GW -> server configuration, if the request from the client is big(greater than communication buffer size) and MONITOR is turned on on gateway, running "force application" command on gateway may cause gateway instance crash.
You can see similar messages in db2diag.log:
2005-06-08-17.01.05.054919   Instance:XXXXXX   Node:000
PID:76504(db2agentg (XXXXX ) 0)   TID:1
Appid:O212DF2D.GF2E.01045B2D1685
DRDA Application Server  sqljsTermAgentReply Probe:10
DIA5000C A DRDA AS token "AGENT TERMINATING" was detected.  The
diagnostic data
returned is (SRVDGN): "SQLERRP:SQLJCMN  SQLCODE:-30081".
ALERT :26
PID:76504 TID:1 Node:000 Title: SQLCA
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -30081   sqlerrml:
37
 sqlerrmc: 32 * 0 TCP/IP SOCKETS 127.0.0.1 send
 sqlerrp : SQLJCMN ?
 sqlerrd : (1) 0x81360012      (2) 0x00000012      (3)
0x00000000
           (4) 0x00000000      (5) 0x00000000      (6)
0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
          (7)      (8)      (9)      (10)        (11)
 sqlstate:
2005-06-08-17.01.05.762408   Instance:XXXXXX   Node:000
PID:76504(db2agentg (XXXXX ) 0)   TID:1
Appid:O212DF2D.GF2E.01045B2D1685
base sys utilities  sqleagnt_sigsegvh Probe:1
Error in agent servicing application with coor_node:
0x2FF19ECC : 0x0000                                     ..
Trap file looks like that:
0xD1F0E0A0 sqljcCompleteDss__FP10sqljCmnMgrl + 0x11C
0xD2CABCA0 sqljrDrdaArDisconnect__FP7UCintfc + 0x244
0xD2510640 sqleuUCagentDrdaArTermConnect__FP7UCintfc + 0x88
0xD250EB68 sqleUCagentConnectReset + 0x148
0xD1CC7DC0 sqljsCleanup__FP13sqle_agent_cbP11UCconHandle + 0x244
0xD1CC7608 sqljsDrdaAsInnerDriver__FP17sqlcc_init_structb + 0x2A0
0xD1CC7440 sqljsDrdaAsDriver__FP17sqlcc_init_struct + 0x134

Local fix

Connect directly to server.

Problem summary

User Affected:
Users who using DB2 gateway and monitor is turned on Problem Description:
If you run DB2 as a gateway, and monitor is turned on in the gateway, you may encounter DB2 crash if you issue "force applicaiton all" command in gateway server.
Problem Summary:
In V8 client -> V8 gateway -> server configuration, and monitor is turned on on the gateway. You may encounter DB2 instance cras h if you running "FORCE APPLICATION" command on the DB2 gateway server. The trap file looks like that:
0xD1F0E0A0 sqljcCompleteDss__FP10sqljCmnMgrl + 0x11C
0xD2CABCA0 sqljrDrdaArDisconnect__FP7UCintfc + 0x244
0xD2510640 sqleuUCagentDrdaArTermConnect__FP7UCintfc + 0x88
0xD250EB68 sqleUCagentConnectReset + 0x148
0xD1CC7DC0 sqljsCleanup__FP13sqle_agent_cbP11UCconHandle + 0x244
0xD1CC7608 sqljsDrdaAsInnerDriver__FP17sqlcc_init_structb + 0x2A0
0xD1CC7440 sqljsDrdaAsDriver__FP17sqlcc_init_struct + 0x134

Problem conclusion

Problem was first fixed in Version 8.1 FixPak 11(also known as Version 8.2 FixPak 4)(s060120)

Temporary fix

Connect to DB2 server directly, don't use DB2 gateway.

APAR Information

• APAR number

  IY73035

• Reported component name

  DB2 UDB ESE AIX

• Reported component ID

  5765F4100

• Reported release

  810

• Status

  CLOSED PER

• PE

  NoPE

• HIPER

  NoHIPER

• Special Attention

  NoSpecatt

• Submitted date

  2005-06-23

• Closed date

  2006-02-05

• Last modified date

  2006-02-05

http://www-01.ibm.com/support/docview.wss?uid=swg1IY73035