PQ52493: WHEN AUTOSTARTING SERVLET GETTING ERROR STACKEMPTYEXCEPTION

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When attempting to autostart a servlet with WebSphere
Application Server 4.0, receiving an error EmptyStackException..
Error shown in RMI registry:
 ExtendedMessage:  Servlet.LOG :."AcordsServlet: Could not bind
 to RMI registry: Exception occurred while getting the homes :;
nested exception is:
  com.netsis.acords.exceptions.AcordsException: error occured in
 getProxyHome: ==|null|=="
When not autostarting the servlet no exception occurs.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere for z/OS and OS/390 v401 users *
*                 who wish to issue JNDI lookups by servlets   *
*                 which are started automatically during       *
*                 Web Container initialization.                *
****************************************************************
* PROBLEM DESCRIPTION: When a JNDI lookup is issued from an    *
*                      auto-started servlet,  a naming         *
*                      exception occurs.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Auto-started servlets did not receive a ThreadContext. This
results in naming exceptions when attempting to issue JNDI
lookups. The same lookup requests function correctly when
issued after Web Container initialization.
Problem conclusion
WebSphere Application Server for z/OS and OS/390 has been
changed to allow java:comp reference lookups from the servlet
lifecycle methods. In particular, this function is now available
for servlets which are automatically initialized during
WebContainer initialization.

Restriction : This function does not support the use of
transactions from within servlet init() methods. The use of
any EJB which requires a transaction environment, such as
TX_REQUIRED or TX_MANDATORY, is not supported when the EJB is
driven from within a servlet init() method.

This change affects COMPID 5655A9800 R401 for z/OS and OS/390.
The code changes are stored in CMVC under defects 79693, 79769,
79787, 79819, 79853, 79964, 80419, 81007, 81078, 81080, 81325,
81517, and 81667.
PQ52493 Documentation Change:

The following restriction will be added to the section "Creating
Enterprise beans" in Chapter 6 of WebSphere Application Server
V4.0.1 for z/OS and OS/390: Assembling J2EE Applications":

Restriction :
The function which allows JNDI lookups from auto-started
servlets does not support the use of transactions from within
servlet init() methods. The use of any EJB which requires
a transaction environment, such as TX_REQUIRED or TX_MANDATORY,
is not supported when the EJB is driven from within a servlet
init() method.
Temporary fix Comments
 **** PE02/05/01 FIX IN ERROR. SEE APAR 
PQ60711  FOR DESCRIPTION
 **** PE02/05/28 FIX IN ERROR. SEE APAR 
PQ61582  FOR DESCRIPTION
APAR information
APAR number PQ52493
Reported component name WEBSPHERE OS/39
Reported component ID 5655A9800
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-09-17
Closed date 2002-04-12
Last modified date 2002-07-12

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJSJPIWA EJSJPIWC EJSJWBJR EJSJWCSC EJSJWCWC EJSPWEAR
EJSPWSAM EJSSMI03 EJSSMI04      

Fix information
Fixed component name WEBSPHERE OS/39
Fixed component ID 5655A9800

Applicable component levels
R401 PSY UQ65118    UP02/04/26 P F204

  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 #: PQ52493
IBM Group: Software Group
Modified date: Jul 12, 2002