PQ77963: 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 PQ77963 addresses various defects  *
*                      in WebSphere Application Server V5.0    *
*                      for z/OS.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ77963 addresses the following defects in
WebSphere Application Server V5.0 for z/OS:

(MD17481) During transactional recovery, the paths to the
resource jars are not appended to the runtime classpath
because the ResourceImpl component is not initialized.  As a
result, the necessary classes were not on the classpath and a
ClassNotFound exception was received.

(MD17489) Users get the following message when security is not
enabled: "BBOS0107E Credential handling function  failed".
Both the controller and servant starts successfully.
This message is issued by an API that is being called when
security was not enabled. This API needs to be called only when
security is enabled.

(MD17494) Internal Failure C9C2116D RC=8 RSN=0F4F086E can
ocur when starting a server out of place. When we start a
controller, we register it with WLM, and then subsequently
report data for the first method in every transaction.  When
starting a server out of place, we do not register the
controller with WLM, but we still report data for each
transaction.  WLM does not know what to do with this data
because the controller never registered with it, so it returns
return code 8, reason 0F4F086E, which WebSphere reports as an
internal error.

(MD17497) During server startup it would be useful to know the
initial set of Java system properties. These properties should
be echoed just as we do the configuration variables during
server initialization.

(MD17506) A customer has the property already preset in their
deployment manager's server.xml to specifiy
"ConnectionIOTimeOut" but the runtime variables:
protocol_http_input_timeout is not being set.
The property ConnectionIOTimeOut in the deployment manager's
server.xml should be "ConnectionIOTimeout".
Both spellings should be accepted.

(MD17509) This is a problem in the administrative console.
The 'weight' field for clusters and cluster members is not
configurable in the console for z/OS.  So, the 'weight' field
should be removed from cluster support.
Navigate to: Servers > Clusters;
This field appears in two place and must be removed from each:
1. new cluster wizard, new cluster member views
2. existing, cluster, add new cluster member views
3. cluster member detail view

(MD17513) Running a workload web application can result in the
following errors:

BBOO0220E SESN0042E: BackedHashtable:ejbCreate - database
error. If a SQLException has occurred then refer to the
appropriate database documentation for your environment. Also,
ensure that you have properly configured a datasource for
Session Manager. . com.ibm.ws.webcontainer.httpsession.
SessionContext com.ibm.ws.webcontainer.httpsession.
SessionContext...

Exception is: com.ibm.websphere.ce.cm.DuplicateKeyException:
DB2JDBCSection Received Error in Method execute:SQLCODE==> -803
SQLSTATE ==> 23505 Error Tokens ==> <<DB2 7.1 SQLJ/JDBC>>
SESSRIND  000000020E

DB2 was trying to store duplicate keys in the DB2 table which
according to specifications of the table were not allowed.  The
SessionId was being truncated to a small value which no longer
made it unique.

(MD17521) A failure can occur during a global transaction after
one or more XA resources have been driven for phase one
(prepare) of two-phase commit, and the time RRS is driven for
phase one of two-phase commit.  In this case, the branches of
the transaction belonging to the XA resources have not been
hardened with RRS.  The transaction service relies on the
recover() method of the XA resource to return these branches.
The transaction service will then drive rollback() for these
branches.

The transaction service drives the recover() method on the next
restart after a server failure.  It is possible that the entries
in the XA partner log (describing the resources on which
recover() should be driven) could be deleted before the
recover() method actually completes.  If the server fails again
during this time, those entries will be permanently lost until
the server drives more work against that resource, and thus
adding it back into the XA partner log.

(MD17532) When the PMI service is enabled, the transaction
service failed to notify the PMI service when a local
transaction completed. The omission of the completed call
results in a growth of the active transactions counter and no
increase in the committed or rolled back counters.
Problem conclusion
APAR PQ77963 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD17481) The path to any resource jars are saved in the XA
partner log so they can be used and added to the classpath
during transactional recovery.

(MD17489) Made the necessary changes to ensure that this API is
not called when security is not enabled

(MD17494) Support was modified to skip reporting to WLM for the
first method in each transaction when starting out of place.

(MD17497) Support has been added to print the system properties
during server startup.

Support for Defect MD17497 requires to following change
to documentation

A change to WebSphere Application Server for z/OS V5: Messages
and Codes GA22-7915-00 will be available in the next refresh of
the documentation. To access the latest online documentation, go
to the product library page at:

www.ibm.com/software/webservers/appserv/zos_os390/library/
________________________________________________________________
BBOJ0077I string
Explanation:  This message is used to display JVM system
   properties at JVM startup.
User Response: None

(MD17506) The transformer was changed to handle both spellings
and the necessary output timer was also set.

(MD17509) The 'weight' field is removed from the following
pages:
      1. create cluster view
      2. create cluster member view
      3. add server to cluster view
      4. cluster member detail view

(MD17513) SessionContext was changed so that the SessID is no
longer truncated to such a small value which no longer makes it
unique.

(MD17521) Code has been added to ensure that no entries are
deleted from the XA partner log until a reasonable attempt has
been made to drive recover() on each XA resource in the XA
partner log.

(MD17532) Local transaction complete calls are now made as
appropriate.

APAR PQ77963 is associated with SERVICE LEVEL W500104 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ77963
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-08-30
Closed date 2003-08-30
Last modified date 2003-10-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced
GA22791500        

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

Applicable component levels
R500 PSY UQ79825    UP03/09/10 P F309

  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: swg1PQ77963.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 #: PQ77963
IBM Group: Software Group
Modified date: Oct 3, 2003