APAR status
Closed as program error.
Error description
Error Message: Customer setup has a very small request timeout value on the client side. The client sends out multiple requests in quick succession, most of which do not receive a reply within the time out period. The logs reveal a lot of requests timing out(CORBA.NO_RESPONSE exception). And the heapdumps taken on the client 30 -60 mins after the test reveal a persistence of com.ibm.rmi.iiop.IIOPInputStream objects. . Stack Trace: N/A .
Local fix
Problem summary
This leak happens because the reply messages received after the request time out period are not cleared properly.
Problem conclusion
The Connection object which holds the reply fragments has been modified to clear fragments corresponding to timed out requests. This fix is available in 1.4.2 SR13 and 5.0 SR9
Temporary fix
Increase request time out (com.ibm.CORBA.RequestTimeout) to a value that ensures that the replies are received within that time. . ZE FIX ERROR IZ78316 in 1.4.2 SR13 FP6
Comments
APAR Information
APAR number
PK73152
Reported component name
JAVA(1.3/1.4 CO
Reported component ID
5648C9800
Reported release
42A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2008-10-04
Closed date
2008-10-31
Last modified date
2010-09-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
JAVA(1.3/1.4 CO
Fixed component ID
5648C9800
Applicable component levels
R42A PSN
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.4.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 February 2022