PK72809: IPC INBOUND ASYNC READ TIMES OUT EVERY 60 SECONDS, THEN immediately goes back to read again.

Fixes are available

APAR status

Closed as program error.

Error description

This APAR corrects the following problems:

1 - Currently IPC connector inbound async read times
out every 60 secs, then immediately goes back to read again.
Although this log has worked correctly, it may be an
efficiency drag, especially on zOS.


2 - Currently SOAP connector only saves user credential
at connector client creation, not at the subsequent calls. So
in a senario such as: Create client to A, create client to B,
use client to A. We should have the credential to A saved, but
instead its remains to be the credential to B, since that
client was last created.

3 - The method RestoreConfigUtility.java::restoreAppBinaries
basically takes each application from repository and extracts
it into target location (typically installedApps directory) as
a part of restore. Each app has a property in deployment.xml
calledenableDistribution.  This decides if the app binaries
should be expanded in target location. The code currently
extracts apps that have enableDistribution set to false which
is wrong.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: Fix several admin problems.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
1 - Currently IPC connector inbound async read times
out every 60 secs, then immediately goes back to read again.
Although this log has worked correctly, it may be an
efficiency drag, especially on z/OS.


2 - Currently SOAP connector only saves user credential
at connector client creation, not at the subsequent calls. So
in a senario such as: Create client to A, create client to B,
use client to A. We should have the credential to A saved, but
instead its remains to be the credential to B, since that
client was last created.


3 - The method RestoreConfigUtility.java::restoreAppBinaries
basically takes each application from the repository and
extracts it into the target location (typically installedApps
directory) as a part of restore. Each application has a
property in deployment.xml called enableDistribution.  This
decides if the application binaries should be expanded in the
target location. The code currently extracts applications that
have enableDistribution set to false which is wrong.

Problem conclusion

1 - The fix is to eliminate the timeout, so that the inbound
async read will standby forever, unless there's an exception,
upon which proper action will be decided.

2 - The fix is to save the credential not only at connector
client creation, but also at their subsequent uses. Thus at
any point the credential saved is certainly the one last used.

3 - The fix is to add a bunch of if statements to fix those
known cases.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK72809
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-25
Closed date
2008-11-03
Last modified date
2008-11-14

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 October 2021

Tips

PK72809: IPC INBOUND ASYNC READ TIMES OUT EVERY 60 SECONDS, THEN immediately goes back to read again.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?