PM56328: INDIRECT JNDI LOOKUPS MAKE REDUNDANT ATTEMPTS TO CONNECT TO AN UNAVAILABLE ENDPOINT.

Fixes are available

APAR status

Closed as program error.

Error description

If a cluster is not available at all, an indirect lookup will
try to contact each cluster member before failing. This is not
an error, but can effect performance.

Local fix

```
na
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server.                                     *
****************************************************************
* PROBLEM DESCRIPTION: Lookups on Indirect JNDI Lookup         *
*                      configured name bindings attempt to     *
*                      connect twice to the addresses          *
*                      contained in the provider URL when      *
*                      the addresses are not available.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Lookups on Indirect JNDI Lookup configured name bindings
attempt to connect twice to the addresses contained in the
provider URL when the addresses are not available. This
doubles the amount of time spent waiting for network timeouts.

Problem conclusion

The problem was corrected by specifiying a default namespace
connection property setting of "eager" to cause initial
context creation to fail immediately instead of deferring the
failure to ensuing lookups on the initial context. If the
binding is configured with a namespace connection property
setting, that setting overrides the default.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.45, 7.0.0.23 and 8.0.0.4. 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
PM56328
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-19
Closed date
2012-03-14
Last modified date
2012-03-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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM56328: INDIRECT JNDI LOOKUPS MAKE REDUNDANT ATTEMPTS TO CONNECT TO AN UNAVAILABLE ENDPOINT.

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?