PQ59546: UNSATISFACTORY RESPONSE AT INITIAL LOGIN OF WEB APPLICATION

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
- Customer is unhappy with WebSphere responsiveness on initial
login to their application.
- Login takes between ten and fifteen minutes for initial
  login to complete.
- Loggin and Introscope-collected data show that JNDI lookups
  are taking the bulk oif the time during startup
- Further research reveals:
  o only lookups issued from the application server (and not
    the web server plugin) are slow
  o Lookups are performed by
    com.ibm.ws.naming.ldap.WsnLdapContextImpl
  o Slow lookups for loading EJBs in the customer application
    consistently taking 8-15 seconds to finish each lookup
  o Each lookup to an EJB results in a new BeanMetaData object
    instance being constructed (on the first lookup to that
    (EJB)
   o Constructing a BeanMetaData object takes 8-15 seconds.
   o In the BeanMetaData object constructor, the
     populateJavaNameSpace2 method takes 1.5 to 2 seconds.
   o In the BeanMetaData object constructor, the
     hetuMofObjects method takeks 1.5 to 2 seconds
   o 69 EJBs are looked up and 69 BeanMetaData objects are
     constructed as part of the initial login-taking
     approximately 10-15 minutes to complete
   o Also of interest:
     - com.ibm.ws390.metadata.ejbjar.Method
        o Approx 400K calls to getEJBName with each BeanMetaData
          construction
        o Approx 100k calls to the "equals" with each
          BeanMetaData construction
   o Customer's deployed EJB Jar is apporx 5mb
   o Customer's ejb-xml is approx 650K
- To be perfectly clear, the slow down does NOT show up in
  subsequent logins
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: EJB init performance needs to be        *
*                      improved when activating an EJB via     *
*                      lookup method.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
EJB init processing has been identified as a performance issue.
EJB init performance needs to be improved during the lookup
method on the EJBHome. On this path there are a large number
of calls to certain methods which could be rewritten to improve
performance.
Problem conclusion
EJB init processing has been modified such that several
highly used methods have been rewritten to reduce the path
length.

APAR PQ59546 is associated with SERVICE LEVEL W401066 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ59546
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-03-28
Closed date 2002-05-20
Last modified date 2002-06-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
UQ66415

Modules/Macros
BBOUBINF BBOZ0812        

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ66415    UP02/05/29 P F205

  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 #: PQ59546
IBM Group: Software Group
Modified date: Jun 5, 2002