PQ55355: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
This APAR addresses defects in WebSphere Application Server
V4.0.1 for z/OS and OS/390.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390.                  *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ55355 addresses various          *
*                      problems in WebSphere Application       *
*                      Server V4.0.1 for z/OS and OS/390.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ55355 addresses the following problems in
WebSphere Application Server V4.0.1 for z/OS and OS/390:

(MD12313) Bootstrap step 12 for J2EE name space fails when
userid and password are from jvm.properties in Systems
Management.

The following is the stack trace you will see in the Systems
Management Server region for this failure:

javax.naming.ConfigurationException: Cannot create Name Tree -
Exception creating Invisible Context: ibm-wsnName=nodeRoot
exception is javax.naming.NoPermissionException: .
LDAP: error code 50 - Insufficient Access Rights.;
remaining name 'ibm-wsnName=nodeRoots'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2664)
at com.sun.jndi.ldap.LdapCtx.processReturnCode
(LdapCtx.java:2602)
at com.sun.jndi.ldap.LdapCtx.processReturnCode
(LdapCtx.java:2412)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext
(LdapCtx.java:652)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.
               p_createSubcontext(ComponentDirContext.java:323)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.
          createSubcontext(PartialCompositeDirContext.java:253)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.
          createSubcontext(PartialCompositeDirContext.java:241)
at com.ibm.ws.naming.ldap.WsnLdapTreeInitializer.
           getInvisibleContext(WsnLdapTreeInitializer.java:180)
at com.ibm.ws.naming.ldap.WsnLdapTreeInitializer.
       createUpperTreeStructure(WsnLdapTreeInitializer.java:73)
at com.ibm.ws390.util._EJSUtilitiesImpl.
           CreateUpperTreeStructure(_EJSUtilitiesImpl.java:311)
at com.ibm.ws390.util._EJSUtilitiesSkeleton.
       CreateUpperTreeStructure(_EJSUtilitiesSkeleton.java:165)

And in a detailed LDAP trace, looking at the ber dump for the
last do_bind entry, you will not see an identity passed and will
see the null dn and ANYBODY being used as the identity.
do_bind:conn 1 version 3 dn () method 128
setting bind type to anonymous
send_ldap_result 0:NULLSTRBUF:NULLSTRBUF
Sending msg to client
ber_flush: 14 bytes to sd 3
+--------------------------------------------------------------+
|OSet| Address = 25914A50  Length = 000E |ASCII  |  EBCDIC     |
+--------------------------------------------------------------+
|0000|300C0201 0161070A 01000400 0400    |0....a.|.../.......  |
+--------------------------------------------------------------+
conn=1 RESULT err=0 nentries=0
do_bind: exit conn->c_dn=CN=ANYBODY, conn->c_version=3

(MD12525) There exists no NLS support for J2EE Resource type
JavaNetURLResource. The J2EE Resource Type property file has not
been translated to Japanese. This will cause English text to be
displayed for J2EE Resource Instances of type JavaNetURLResource
on the WebSphere for z/OS Administration Application (SM EUI).

(MD12535) A COMM_FAILURE exception C9C21149 is thrown trying to
commit a transaction when the Control Region being used by the
client is Stopping.

The following errors are logged during the commit of a
transaction while the Control Region involved is stopping.
Note that the port (0) in the EDC8116I message is important.
This problem occurs because the Daemon incorrectly fails locate
processing for a Transaction object looking for a specific
Control Region that is stopping.

Trace: 2001/10/25 08:59:18.385 01 t=9F9680 c=UNK key=P8
(0000000A
 Description: Log Boss/390 Error
 from filename: ./bbocsess.cpp
 at line: 4340
 error message: BBOU0639E Function connect() failed with RV=-1,
 RC=1116, RSN=766303FF, .EDC8116I Address not available..
 hostname
 /ip: xx.xx.xx.xx  port: 0
 Trace: 2001/10/25 08:59:18.386 01 t=9F9680 c=UNK key=P8
 (0000000A
 Description: Log Boss/390 Error
 from filename: ./bboocomm.cpp
 at line: 4032
 error message: BBOU0051E Internal communications error:
    REASON=C9C20C30.
 Trace: 2001/10/25 08:59:18.387 01 t=9F9680 c=UNK key=P8
 (00000004)
 Description: Throw CORBA system exception
 exception id: CORBA::COMM_FAILURE
 minor code: c9c21149
 from filename: ./bbooreq.cpp
 at line: 723

(MD12546) RAS Trace information for HTTP requests is incomplete
or wrong. The Trace entry correlator C=x.y (bborto.cpp) contains
a Session Instance count and a Comm request Id.  The correlator
displays as either C=UNK for unknown or C=2.somehexstuff for
HTTP Request flows.

Also, the trace records that list the hostname have
"hostname=HTTPTYPE port=?" in them for HTTP flows. They should
indicate the ip address of the client and port of the client
such as we do in IIOP.

(MD12602) The StaleConnectionException class needs to be shipped
in ws390srt.jar so users migrating applications
from WebSphere Advanced Edition V4.0 to WebSphere Application
Server V4.0.1 for z/OS and OS/390 do not get a
NoClassDefFoundException exception.

(MD12609) Within the WebSphere for z/OS SMF records for the J2EE
container (subtypes 5 and 6), strings that are longer than 256
bytes (128 doublebyte characters) are truncated.

Each of the following strings gets truncated if it is longer
than 256 bytes:
  containerName
  beanAMCName
  methodNameAndSignature
  methodRoles
If the string is longer than 256 bytes, only the rightmost
block of up to 256 bytes is copied into the SMF event.
For example: if the original string length is 260 bytes, and the
byte array positions are initialized like shown here:
  0   - x
  ...
  254 - a
  255 - b
  256 - c
  257 - d
  258 - e
  259 - f
then the resulting string is "cdef" with the leading 256 bytes
truncated.

(MD12611) Message BBOJ0014I displays a blank string for the
caller identity. The problem occurs when a caller tries to
access a method for the first time, without the proper
authorization. Normally the message will get the caller
identity by looking into the stack and retrieve the identity
of the current element. If this is the first method in the
application, the stack would be empty, and the message will
get back a null string.

(MD12622) The "Method name and signature" field in EJB container
SMF records (subtypes 5 and 6) contains invalid data. Originally
the format for those fields was
"method_name:method_parameterlist".  Due to a recent change, the
current format in the SMF records is
"method_name:method_name(method_parameterlist)".
However, the SMF browser tool as it is delivered currently shows
"method_name:method_name" only.
only.

(MD12630) New work may be accepted for a Server started out of
place. Code in activateListeners(), bbocsmgr.cpp, only checks
for a restart out of place if arm restarted.  This will allow a
Server that was restarted out of place to register with WLM and
be eligible for new work.

(MD12697) Transactions using ADCT1 may not be resolved during
restart. If a transaction uses the new RRS ADCT1 functionality,
and has subordinate interests, and one of the servers running
the transaction fails during ADCT1, any transaction that comes
up in-doubt on restart may not be resolved.  This would require
the user to go to the ATRFPCMN panel and manually resolve these
transactions. The ADCT1 functionality will be delivered in RRS
APAR 
OW50074.

(
PQ49545) Insufficient diagnostics when naming registration
of an ejb fails. WebSphere for z/OS attempts to register the
homes of a newly imported EJB application into the JNDI name
space the first time the server where the EJB was installed
is started.  This is indicated by the following message:
BBOU0694I NAMING REGISTRATION STARTED FOR
                     SERVER <servername>
When the naming registration fails, then the following
message is issued:
BBOU0652E NAMING REGISTRATION FAILED FOR SERVER
                     <servername>
No indication is given as to why the registration failed.  It
is typically due to missing classes during the loading of the
bean meta data.  The missing class name can only be found
by turning on trace and best found by turning on java trace
(JVM_DEBUG=1).  It should be more apparent to the user
why the failure occurred.

(
PQ54064) When running with different levels of the client and
server JDK ORB, a customer may receive CORBA::MARSHAL exceptions
with a minor code of zero (or 4942F000). Different service
levels of the marshalling code may result in incompatabilities
as data is marshalled in a lower service level and demarshalled
by a newer service level of marshal code, or vice versa. These
problems surface as a CORBA::MARSHAL exception, usually with a
zero or 4942F000 minor code.
Problem conclusion
APAR PQ55355 provides the following problem resolution:

(MD12313) EJSUtilitiesImpl.CreateUpperTreeStructure was updated
to set the userid and password into the Hashtable used as the
parameter list to
WsnLdapTreeInitializer.createUpperTreeStructure(treeInitParms)
no matter if they came from the jvm.properties file or the
current.env file.

(MD12525) The property file JavaNetURLResource.properties
has been translated the Japanese and is installed in the
resources templates directory as
JavaNetURLResource_ja_JP.properties.

(MD12535) The fact that the Control Region is stopping should
not be involved in the decision of whether to allow a locate for
a direct-reference to find that Control Region.  Modules
bbocasyd and bboclspc have been changed to not limit direct
searches to non-stopping control regions.

(MD12546) Communication Session manager (bbocsmgr.cpp) has been
updated to provide Communication Session Instance counts that
are now unique across all Session protocols.  This value is used
in the trace correlator area to relate trace entries.

For HTTP communication protocol, RAS Trace entries containing
the partner routing information, "sent to:", will now have the
IP Address and Port number of the foriegn partner.  Also, for
HTTP Sessions a comm request id (part of the correlator in a
RAS Trace entry) will be generated for inbound requests.

(MD12602) The StaleConnectionException class has been shipped in
ws390srt.jar so users migrating applications from WebSphere
Advanced Edition V4.0 to WebSphere Application
Server V4.0.1 for z/OS and OS/390 do not get a
NoClassDefFoundException exception.

(MD12609) Support have been added for WebSphere for z/OS SMF
records for the J2EE container (subtypes 5 and 6), such that
strings than 256 character in length are nolonger truncated.

(MD12611) Processing for message BBOJ0014I has been modified
such that a check for returned subject being null will be made.
If this is the case, instead of returning a null string a call
will be made to get the current identity of the subject. Once
the subject identity is determined the caller identity can be
obtained.

(MD12622) The SMF base code and the SMF browser were modified to
produce and show EJB method name and signature related fields in
the format "method_name(method_parameterlist)".

(MD12630) Code in activateListeners(), bbocsmgr.cpp, is changed
to invoke BBO_ENQS::running_where_configured(),
bbo3enqs.cpp, to determine if it is restarted out of place.

(MD12697) Support has been added to check to see if there are
subordinate interests before allowing the use of ADCT1. If there
are subordinate interests, use ADCT or two-phase commit instead.

(
PQ49545) New message, BBOJ0016E will be issued to report
ClassNotFound exceptions.  The message will indicate the name
of the EJB being processed as well as the name of the missing
class.

(
PQ54064) To handle imcompatabilities between marshalling code,
the JDK ORB implemented the Partner Version service context.
WebSphere Application Server V4.0 for z/OS uses the JDK ORB, but
did not exploit this service context.  Code has been added to
exploit this service context thus allowing different levels to
co-exist.

The following publication was revised as a result
of APAR PQ55355:
________________________________________________________________
WebSphere Application Server V4.0.1 for z/OS and OS/390
Messages and Diagnosis
GA22-7837-02
________________________________________________________________
This APAR requires changes to documentation.

NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:


http://www.ibm.com/software/webservers/appserv/

________________________________________________________________
Chapter 12, pg. 222 (new message)
BBOJ0016E Could not load EJB <beanname> - Class <beanclass> not
          found.
Explanation: An error message issued when loading an EJB.
             The specified class could not be found.
Programmer response: Add missing class to the EJB jar file and
                     re-install J2EE application.
________________________________________________________________
Chapter 13, pg. 339 (new message)
C9C20CE9
Explanation: getRemoteName is passed a buffer to place message
text into.  The buffer wasn't big enough for the text that was
to be put into it.  Most probably a code error or an overlay
occurred. This check is to prevent an accidental overlay.
User Response: IBM Internal Only
________________________________________________________________


APAR PQ55355 is associated with SERVICE LEVEL W401009 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ55355
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-11-30
Closed date 2002-01-02
Last modified date 2002-05-19

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOAPCEI BBOAPCWI BBOAPIAI BBOAPIOI BBOAPXLI BBOAXCEI
BBOAXIAI BBOBOA BBOCASYD BBOCCFMT BBOCHSES BBOCLSPC
BBOCOMM BBOCORBA BBOCPOCB BBOCSESS BBOCSMGR BBOCSMRH
BBOCSMRI BBOCSMRL BBOCSMRS BBODDAUT BBODDDEF BBOFRCGD
BBOIBOIM BBOIDRMI BBOIGTID BBOIIMA BBOIIMC BBOIKEYS
BBOIRDB BBOIROOT BBOITLS BBOI3PLI BBOJJU BBOLORB
BBOLRT BBOMDDLO BBOMIBO BBOMICP BBOMIDO BBOMSBO
BBOMSCO BBOMUTIL BBOOAACI BBOOABM BBOOACCI BBOOACQE
BBOOACQW BBOOACRT BBOOAET BBOOAGEV BBOOAIM BBOOAIMR
BBOOAIMS BBOOAMR BBOOAPBC BBOOAPCI BBOOARCI BBOOARMR
BBOOARMW BBOOAS1 BBOOAS2 BBOOAS3 BBOOBOAI BBOOBOAT
BBOOCOMH BBOOCOMM BBOOCRHT BBOOCSIT BBOODGAI BBOODGCA
BBOODQCA BBOODQEB BBOODRAI BBOODSAB BBOODSM BBOOEJSB
BBOOEVAS BBOOHA BBOOJORB BBOOORB BBOOORBR BBOOSMFP
BBOOSMFR BBOOSMFT BBOOSMFW BBOOSMOI BBOOSRWT BBOOSS
BBOOTMOT BBOOTRD BBOPBO BBORAS BBOSEC BBOSEXT
BBOSLHM BBOSNMO BBOSQ03 BBOTOTSJ BBOTSUW BBOTTF
BBOTTSR BBOUBINF BBOZ0229 BBOZ0663 BBOZ0812 BBOZ0813
BBOZ0916 BBOZ0917 BBOZ0918 BBOZ0919 BBOZ0920 BBOZ0921
BBOZ0922 BBOZ0923 BBOZ0924 BBOZ0925 BBOZ0926 BBOZ0927
BBOZ0928 BBOZ0929 BBOZ0930 BBOZ0931 BBOZ0932 BBOZ0933
BBOZ0955 BBOZ0957 BBOZ0959 BBOZ0961 BBOZ0963 BBOZ0965
BBOZ0967 BBOZ0976 H28W401J      

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ61607    UP02/01/15 P F201

  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 #: PQ55355
IBM Group: Software Group
Modified date: May 19, 2002