PQ81152: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V5.0 FOR Z/OS.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
This APAR addresses defects in WebSphere Application Server
V5.0 for z/OS.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ81152 addresses various defects  *
*                      in WebSphere Application Server V5.0    *
*                      for z/OS.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ81152 addresses the following defects in
WebSphere Application Server V5.0 for z/OS:

(MD18244) Ship Webservices Gateway (WSGW) as a Techpreview.

(MD18254) MDB not receiving messages when security is enabled.
During MDB registration, connection browsers are to be created
in the controller region. In order to do that MQ connections are
required and when an attempt is made to create the connection
it fails with the error message:
MQJE001: An MQException occurred: Completion Code 2, Reason 2063
This is due to the username and password not being used when
creating the connection. This problem manifests itself when
security is enabled and MDB messages are to be listened for by
the controller region.

(MD18269)  Can not change JMS server short name in panels.  As
a result, user can not install more than one IJP (Integral JMS
Provider). Even though there is support for multiple IJPs, there
is no way to set this up with the dialog.  The server short name
is defaulted to WMQX and can not be changed in the dialog panels
for the IJP customization.

(MD18275) Accessing attributes of Beans caused a
com.ibm.db2.jcc.DB2SQLException.

Received exception:
com.ibm.db2.jcc.DB2SQLException: DB2JDBCCursor Received Error in
Method prepare:SQLCODE==>  -473 SQLSTATE ==> FFFFF
Error Tokens ==> <<DB2 7.1 SQLJ/JDBC>> at
COM.ibm.db2os390.sqlj.jdbc.DB2SQLJJDBCCursor.setError
(DB2SQLJJDBCCursor.java:1207)

(MD18287) InstanceNotFoundException generated in servant region
when a dynamic MBean proxy invokes the wrong servant. The JMX
servant MBean invoker facility for dynamic MBean proxies should
not invoke servants on which the subject MBean does not reside.
(That is, the dynamic proxy must not assume that each servant
has an instance of the servant MBean associated with the proxy.)

(MD18288) Failure during preInvoke() when invoking an EJB with
a previously cached connection from within a global transaction.
Message J2CA0058E may appear. One scenario in which the problem
occurs would be: Method A is invoked on EJB 1, and begins a
global transaction. Method A invokes Method B of EJB 2, a
stateful session bean. EJB 2 caches the JDBC Connection which it
obtains during Method B. Method A then invokes Method C on the
same instance of EJB 2, and the failure occurs during preInvoke
for Method C.

Error messages like the following may be seen:

J2CA0058E: The ConnectionManager was unable to associate
Connection  XXXXXXX  with ManagedConnection XXXXXXXX

Received exception: javax.resource.ResourceException:
Current UOW does not match the UOW with which the
 ManagedConnection is already enlisted.
 at com.ibm.ejs.j2c.ConnectionManager.reAssociate(...)
 at com.ibm.ejs.j2c.HandleList.reAssociate(...)
 at com.ibm.ejs.j2c.HandleCollaborator.preInvoke(...)
 at com.ibm.ejs.container.StatefulBeanO.preInvoke(...)
 ..... stack trace continues down....

(MD18289) Specifying "Y" to the Customization Dialog's "Use
SAF EJBROLE profiles..." does not result in the profiles being
generated. The customization dialog contains an option for
generating EJBROLES profiles in the Security Domain section.
However, because of a mismatch between the variable being set
and the  variable being tested, the proper RDEFINE and PERMIT
commands are not generated when the user specifies "Y".

(MD18291) In a cell with Security enabled, when the Node Agent
attempts to communicate with the DeploymentManager for the first
time after addNode, a javax.net.ssl.SSLHandshakeException
unknown certificate is found in the joblog.

The exception:

 SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening
socket: javax.net.ssl.SSLHandshakeException: unknown
certificate; targetException=java.lang.IllegalArgumentException:
Error opening socket: javax.net.ssl.SSLHandshakeException:
unknown certificate

The exception is caused by a mismatch in the default sslConfig
of the Nodeagent and the DeploymentManager.

(MD18296) Certain PMI metrics that are suppose to always
increase over time, such as 'total number of requests sent to
the ORB,' are decreasing when servants terminate.

While using Tivoli Performance Viewer to monitor performance
data, the performance data that are monotonically non-decreasing
actually decrease over time especially when servants are being
terminated as if terminated servants' data is getting lost
due to lack of performance data storage in the controller side
PMI related MBeans.

(MD18336) NullPointerException raised during installation of
application that contains a null value for an env-entry.
When an application contains a null value for an env-entry
that is defined on the application, and the application
contains a custom finder, then a NullPointerException will be
raised during application installation, causing the application
to fail initialization. This occurs when the container
attempts to query the env-entries for custom finder
enhancement settings and  processes a null value.

(MD18341) Dialog generated job BBOWSAMR needs to get updated
to pick up the new WebServices samples.

(MD18363) Unable to read MBean descriptor (xml file) in
controller region. MBeans that are contained within an
application's ear file are dependent on the application
classloader for reading the MBean descriptor (xml) file. The
descriptor file is required in both the servant region (when
creating the MBean) and the controller region (when creating the
dynamic MBean proxy). However, the application classloader is
not available in the control region, resulting in a failure to
load the descriptor file. This causes a
java.io.FileNotFoundException (which contains the relative
pathname of the descriptor file) to be thrown in the servant
region, which causes the MBean registration to fail. (This
exception is generated within the control region and sent back
to the servant region within a java.rmi.RemoteException.)

(MD18366) Manual changes to the plugin-cfg.xml file are not seen
when displayed using the administrative console.

Manual changes made to the IBM Http Server plugin configuration
file plugin-cfg.xml are not displayed when the view
configuration button is pressed in the admin console. This
happens because two files were kept when the generate button was
pressed in the admin console: the ebcdic file plugin-cfg.xml
containing the IBM Http Server plugin configuration, and the
ascii file plugin-cfg-ascii.xml, displayable at the browser,
containing the same information. When the plugin-cfg.xml file
is manually editted, changes made there are not automatically
included in the plugin-cfg-ascii.xml file.
Problem conclusion
APAR PQ81152 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD18244) The Webservice gateway shippables are now being
shipped to the WebServicesGatewayTechPreview directory off of
<WAS_HOME>.

****************************************************************

Defect MD18244, shipped in Cumulative Fix W502000, requires the
following documentation change:

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:

www.ibm.com/software/webservers/appserv/zos_os390/library.html
________________________________________________________________
WebSphere Application Server V5 for z/OS
Messages and Codes
GA22-7915-00
_______________________________________________________________
Chapter 1, pg. 73 (new message)
BBOO0270E WEBSPHERE APPLICATION SERVER FOR Z/OS LICENSING
   AGREEMENT NOT MET
Explanation:
 For customers who are applying the program on top of existing
 configurations of WebSphere Application Server for z/OS version
 5.0, you will also be required to review and indicate
 acceptance of additional terms.
User Response:
 You access these additional terms as follows:

 1. Invoke the Configuration Dialog.

 2. You will be presented with these additional
    licensing terms & conditions upon invocation of the
    Configuration Dialog.

 3. After reading the additional terms, you will be
    prompted for acceptance. If you do not accept these terms,
    execution of the code will be denied.

 4. Once you accept, you will be on the main panel of the
    dialog.  Select the option
      "Configure v5.02 License Agreement Refresher."

 5. Follow through the option "Configure v5.02 License
    Agreement Refresher." to generate the jobs and
    follow the generated instructions.

 6. You need to repeat step 5 for each hfs for WebSphere
    configuration data, WAS_HOME
    (for example /WebSphere/V5R0M0/AppServer), that you
    have configured.

(MD187254) Utilize the username and password obtained from the
password credential associated with the connection factory for
which the MDB is listening. This is done during the creation
of the MDB resources (factory and connection) at the servant
region.

(MD18269) The WebSphere for z/OS Customization dialog will be
updated to enable the JMS server short name to be configurable.
The user will be able to install more than one IJP.

(MD18275) Shipping the updated ejbdeploy code which fixes this
issue and some other issues:
- Attributes of type long in a CMP bean and used in a finder
(via EJB QL) had their SQL generated to CAST the value to
BIGINT.  BIGINT is not allowed on zOS.
- Inheritance - create of child adds values to columns in parent
table.
- An attribute of type String used in a finder (via EJB QL) had
their SQL generated to CAST the value to VARCHAR(32672); this
causes DSNT408I SQLCODE = -134, ERROR:  IMPROPER USE OF LONG
STRING COLUMN  OR AN EXPRESSION OF MAXIMUM LENGTH GREATER THAN
255
- Attribute defined as char type in backend DB2 7.2 for
workstation will not deploy. This occurred with multiple
backends defined.

(MD18287) In the case that a single servant MBean is to be
invoked, the JMX dynamic proxy support now verifies that the
target MBean resides on the selected servant before it attempts
to invoke the MBean. Likewise, when sending an MBean request to
all servants, the JMX dynamic proxy support now only invokes
those servants in which the target MBean actually resides.

(MD18288) Fixed ConnectionManager to use equals(), not ==, to
correctly compare transaction objects.

(MD18289) The code was changed to test for the same variable
that the Customization Dialog sets. Now, if the user
specified "Y" to the question "Use SAF EJBROLE profiles...",
the RDEFINE and PERMIT commands are generated.

(MD18291) Code was changed to make the NodeAgent's default
sslConfig match the default of the DeploymentManager.

(MD18296) Current PMI MBeans need to be enhanced to be able to
store terminated servants' performance data in support of
monotonically non-decreasing performance data. PMI MBeans will
take advantage of dynamicproxy MBean handlers such as
EventHandler, StateObject, and AggregationHandler to keep track
of terminated servants' performance data within dynamicproxy
MBean running under the controller process.

(MD18336) Modified the container to protect against a null value
set within a given env-entry defined on a bean.

(MD18341) Dialog skeletons BBOWSAMR has been updated to add
the new WebServices samples.

(MD18363) When the servant MBean is created, a call is made to
the controller region to create the MBean proxy. The servant has
been modified to load the descriptor file into a byte array and
pass this byte array to the control region. The controller
region now uses this byte array to obtain the descriptor
information, rather than reading the descriptor file.

(MD18366) Changes are made to IBM WebSphere Application Server
for z/OS such that only plugin-cfg.xml is created or modified.
That file is displayed when the admin console view configuration
button is pressed.

APAR PQ81152 is associated with SERVICE LEVEL W502000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ81152
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-11-19
Closed date 2003-12-07
Last modified date 2004-01-03

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOANINS BBOCASYD BBOCFRAG BBOCSICR BBOCSMRP BBODASRS
BBODASRU BBODCFG2 BBODEFR BBODE2AS BBODRMAK BBOHJM
***This field was truncated. To obtain
the full apar record, please contact
your local support center.***    

Publications Referenced
GA22791500        

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ82903    UP03/12/15 P F312

  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


Current web document: swg1PQ81152.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ81152
IBM Group: Software Group
Modified date: Jan 3, 2004