PQ73506: SQLCODE -913

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
A thread invoked a serialized method and is waiting on
a reply from DB2 -- the related TCB had the following traceback:
   007D8B58
   @@FECBBPX1TAF
   @@GETFN
   SQLJTAFS
   sqlj_ctxTakeContext
   sqlj_ctxSetContext
   sqlj_DSNHLI
   Java_COM_ibm_db2os390_sqlj_jdbc_DB2SQLJJDBCSection_native_1J
   COM/ibm/db2os390/sqlj/jdbc/DB2SQLJJDBCSection.native_JDBCPre
   mmipSelectInvokeJavaMethod
   ---->COM/ibm/db2os390/sqlj/jdbc/DB2SQLJJDBCSection.prepare()
    The parameter list for the BPX1TAF call shows the first
parameter being the routine address and the third
parameter being the target thread identifier of the running
routine. The traceback for the target thread was:
DSA Addr  Program Unit  PU Addr   PU Offset  Entry
 2C55D4D0                0662E188  -059E268A  __server_pwu
 2C55D408                2CB70548  +000000E6  HTQueue_RecvWork
 2C55D308                2CBB5A98  +00000142  HTWorkQueue
 2C55D168                2CAB6240  +00000762  HotThread
 2C55D0B0                0684C790  -00000106  CEEPGTFN
7F60AB98  CEEOPCMM      00C642F0  +00000926  CEEOPCMM

    The application has issued a Pthread_affinity call to run
a routine on a thread that has yet to return from __ser
call. The function codes passed were SRV_GET_WRK + SRV_END_WRK
+ SRV_DEL_ENC. We are in the get_wrk call to WLM after having
done the  END_WRK and DEL_ENC (delete enclave). The BPX1TAF call
can not complete until we come back from WLM.
    Thus the resultant SQLCODE -913.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 version 4.0.1 for z/OS and OS/390.           *
****************************************************************
* PROBLEM DESCRIPTION: Timeouts sometimes occur when DB2       *
*                      accesses the sessions table with the    *
*                      HTTPD Server running in scalable mode.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If a thread processing an http request locked an HttpSession in
DB2 and did not save the HttpSession to DB2 before returning
to the HTTPD Server for more work, timeouts would sometimes
occur.
Problem conclusion
An HttpSession is saved to DB2 before the thread which locked
it returns to the HTTPD Server to process other http requests.

APAR PQ73506 is associated with SERVICE LEVEL W401505 of
WebSphere Application Server version 4.0.1 for z/OS and OS/390
Temporary fix Comments
APAR information
APAR number PQ73506
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-04-24
Closed date 2003-05-14
Last modified date 2003-06-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJSJWC04          

Fix information
Fixed component name WEBSPHERE OS/39
Fixed component ID 5655A9800

Applicable component levels
R401 PSY UQ76901    UP03/05/19 P F305

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ73506
IBM Group: Software Group
Modified date: Jun 5, 2003