PQ51904: MAKE STANDARD (I.E. NON-CUSTOMER) J2EE APPS READ ONLY IN SM EUI

APAR status
Closed as fixed if next.

Error description
When attempting to run the WAS 4.0 Web Application IVP the
following error message appears:
javax.naming.NameNotFoundException:
                         [LDAP: error code 32 - No Such Object];
                             remaining name 'ibm-wsnName=PLUGIN'
This occurs because the customer has deleted the application
RemoteWebContainer.  This application is required to run the
Web Appl.IVP, or any J2EE appl.. It is automaticaly deployed for
every J2EE server.  Therefore this application should be
'protected' so that it can not be deleted from any J2EE server.
                                                               .
Another symptom of this error scenario is to run this query:
   export LDAP_BASEDN="o=WASNaming,c=US"
   ldapsearch -v -p 1389 "objectclass=*" > name.space
In name.space there will be no instance of "PLUGIN".
Local fix
To recover from this error situation you will need to delete and
redefine your server.  The creation of a 'new' server will cause
the automatic creation of the RemoteWebContainer application on
the server.  Then once your other applications are deployed on
the server you should be able to successfully run web clients
that execute your application, be it the IVP or other customer
defined application.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390.                    *
****************************************************************
* PROBLEM DESCRIPTION: The web container application           *
*                      "RemoteWebContainer" which is installed *
*                      automatically on each J2EE server can   *
*                      be deleted without special warning,     *
*                      causing web applications to fail during *
*                      runtime with an LDAP rc 32 in the       *
*                      application server server region.       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The web container application "RemoteWebContainer" is deployed
automatically on every J2EE server. This application is
required to run the web application IVP, or any J2EE web
application. If the "RemoteWebContainer" application is deleted
by mistake, web applications fail during runtime with the
following error message:
  javax.naming.NameNotFoundException:
  LDAP: error code 32 - No Such Object ;
  remaining name 'ibm-wsnName=PLUGIN'
Another symptom of this error scenario is to run the query:
  export LDAP_BASEDN="o=WASNaming,c=US"
  ldapsearch -v -p 1389 "objectclass=*" > name.space
In name.space there will be no instance of "PLUGIN" for the
server experiencing the NameNotFoundException.

To recover from this error situation the J2EE server has to be
deleted and redefined. The creation of a 'new' server will cause
the automatic deployment of the RemoteWebContainer application
on the server.  Then once the other applications are deployed on
the server the web applications should run successfully.

In the future the WebSphere for z/OS Administration Application
(SM EUI) will issue a warning before the "RemoteWebContainer"
application is deleted. The new message is:

  BBON0564I The J2EE Application RemoteWebContainer you are
  about to delete was system generated. Delete cannot be undone.
  Are you sure you want to delete?

The help for the message is:
  Within WebSphere Application Server for z/OS there are a
  number of objects that have been created by the system itself,
  rather than by the user. These objects are displayed on the
  administration user interface next to the objects defined by
  the user. Some of these objects are required by the system at
  any time, some of them are only needed for specific functions.
  Deleting any of these objects will always result in a lack of
  function. It is highly recommended not to delete any of them,
  unless you are 100% sure which function will be affected by
  doing so.
Problem conclusion Temporary fix Comments
This APAR is being closed FIN with concurrence from the
submitting customer. A solution to this problem will be
delivered in a WebSphere Application Server for z/OS
and OS/390 release within the next 18 months.
.
A fix for the problem reported by this APAR has been
provided in PTF UQ58507 of WebSphere Application Server
V4.0.1 for z/OS and OS/390.
APAR information
APAR number PQ51904
Reported component name WEBSPHERE OS/39
Reported component ID 5655A9800
Reported release 400
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2001-08-28
Closed date 2001-10-05
Last modified date 2002-07-24

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R400 PSN    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ51904
IBM Group: Software Group
Modified date: Jul 24, 2002