PM99139: POOR PERFORMANCE DOING LOOKUP OF OBJECT IN JNDI PARTICULARLY WHEN USING DSMLCTXFACTORY AND DSMLCTX.

Fixes are available

APAR status

Closed as program error.

Error description

Poor performance is observed when looking up an object in JNDI
with certain types of objects and particularly when using
com.sun.jndi.DSMLCtxFactory and com.sun.jndi.DSMLCtx.

Javacores show threads frequently a toString() method of a
class related to the object being looked up (a DSML class in
the case of DSML).  This toString() methods is called
indirectly from either:

org.apache.aries.jndi.DirObjectFactoryHelper.doGetObjectInstance
or
org.apache.aries.jndi.ObjectFactoryHelper.doGetObjectInstance

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Poor performance during lookup in       *
*                      JNDI of certain types of object, in     *
*                      particular DSML objects.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Fix pack 8.0.0.2 introduced new trace into
org.apache.aries.jndi.DirObjectFactoryHelper and
org.apache.aries.jndi.ObjectFactoryHelper which was not
guarded correctly.  As a result, the toString method of
objects related to the lookup were called even if trace was
not turned on.
If the toString method was expensive, as is the case with
DSMLCtx when the DSML file is large, poor performance is
observed during lookups.

Problem conclusion

This APAR resolves the problem by correctly guarding the trace
to avoid always calling the toString methods of objects
related to the lookup.

The fix for this APAR is currently targeted for inclusion in
fix pack 8.0.0.9.  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
PM99139
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-10-15
Closed date
2013-11-11
Last modified date
2013-11-11

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

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":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 April 2022

Tips

PM99139: POOR PERFORMANCE DOING LOOKUP OF OBJECT IN JNDI PARTICULARLY WHEN USING DSMLCTXFACTORY AND DSMLCTX.

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

R800 PSY

Document Information

Share your feedback

Need support?