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

(MD15506) In-doubt XA transaction branches coordinated by
WebSphere for z/OS may be ignored at restart if they were
enlisted in a subordinate branch of an OTS transaction that
originated in a non-WebSphere for z/OS server.

When an interoperable transaction context is received from a
non-WebSphere for z/OS server, the XIDs generated for
XAResources enlisted in the local branch contain the formatID
from the inbound OTS transaction identifier instead of the
WebSphere for z/OS specific formatID.

During recovery, WebSphere for z/OS is responsible for
identifying XIDs returned by a JTA/XA based connectors that it
has generated and to ignore XIDs that it did not.  When the
formatID does not match the WebSphere for z/OS formatID, the
XID is ignored and no recovery is attempted - even if the XID
was generated by the local coordinator.

(MD15746) Support is needed to alphabetize print of
configuration variables that show up in job log of
the Daemon, Control, and Servant process.

(MD15927) HTTP Sessions are lost when running with multiple
Servant Regions. HTTP requests are not being correctly routed to
the correct Servant Region where the session was created.  This
causes the HTTP sessions to be lost when running with session in
memory.

(MD16320) Passivated expired Stateful Session Bean file not
deleted from the passivation directory.

All Stateful Session Beans are passivated to the passivation
directory when servers are stopped normally. Stateful Session
Beans with an activation policy of transaction are activated and
passivated at the beginning/ending of a transcation. If these
Beans are not referenced again after they have been passivated
the file will not be removed from the passivation directory
when the Beans timeout value has been reached. If there are
a large quanity of these Beans then there is a small chance
that the volume that contains the passivation directory may
become full.

(MD16350) A message indicating that Single Sign-On (SSO)
is not enable is displayed in the server region, even though SSO
 is enabled. This is
the actual message:

BBOS1000W  LTPA or ISCF are configured as the
authentication mechanism but SSO is disabled.

An incorrect check is made to query if SSO was enabled or not.

(MD17050) SOAP and RMI connectors fail to start when server is
started out of place.

The SOAP and RMI connectors start in the controller and bind to
the ports that they were configured to.  When the controller is
starting out of place, these ports may already be in use by
another server configured on this system.  The bind may fail
and the controller will come down, unless the configuration
uses unique port numbers across the entire sysplex.
Problem conclusion
APAR PQ78451 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD15506) The formatID is now changed when WebSphere for z/OS
generates the transaction identifier for the local branch of the
interoperable transactions.  This change results in the proper
formatID in XIDs generated by WebSphere for z/OS in all cases.

(MD15746) Support has been modified to print configuration
variables alphabetazied.

(MD15927) The Control Region code will be changed to correctly
generate the token that represents the session that got
registered by the Servant Region that created the http session.

(MD16320) Support was added to check the passivation directory
periodicaly for Stateful Session Beans that have timed out. If
they are timed out the file is removed. The interval is
controlled by the JVM system property
com.ibm.websphere.bean.delete.sleep.time.
The default time is 70 minutes(4200 seconds). The value can be
changed from the Administrative Console. To change the value
connect the Administrative Console and navigate to the Java
Virtual Machine Custom Properties panel. For example it would be
the following for server1 control process.
Application Server>server1>Process Definitions>Control>Java
 Virtual Machine>Custom Properties.
If the com.ibm.websphere.bean.delete.sleep.time
property is not present in the list, click new, enter the
property name in the name field and the value in the value
field. The value is the time to wait between checking for timed
out beans. It is in seconds. For example: 120 would be 2
minutes. This same property controls the interval in the Servant
process used for checking for timed out beans that are still
active in the EJB container.

Defect MD16320 requires the following documentation change:
The following  description of the
com.ibm.websphere.bean.delete.sleep.time property
will be added to the new InfoCenter article "Example:
Setting Custom JVM Properties" which will be added to the z/OS
view of the WebSphere Application Server V5 InfoCenter.

com.ibm.websphere.bean.delete.sleep.time
Specifies the time between sweeps to check for timed out beans.
The value is entered in seconds. For example, a value of 120
would be 2 minutes. This property also controls the interval in
the Servant process that checks for timed out beans still
visible to the EJB container.

The default value is 4200 (70 minutes). The minimum value is
60 (1 minute). The value can be changed through the
administrative console. To apply this property, you must
specify the value in both the Control and Servant JVM Custom
Properties.

Steps for this task:

1. Connect to the administrative console and navigate to the
   Java Virtual Machine Custom Properties panel. For example,
   Application Server >server1 > Process Definition > Control >
   Java Virtual Machine > Custom Properties to define the
   property in the Control, or Application Server >server1 >
   Process Definition > Servant > Java Virtual Machine >
   Custom Properties to define the property in the Servant.
2. If the com.ibm.websphere.bean.delete.sleep.time property is
   not present in the list, create a new property name.
3. Enter the name and value.


This article will be available in the next refresh of the
InfoCenter. To access the InfoCenter, go to the product
library page at URL:

www.ibm.com/software/webservers/appserv/zos_os390/library/

(MD16350) Code was added to fix the check for SSO enabled. The
message BBOS1000W is issued only when SSO is not enabled.

(MD17050) Since the SOAP and RMI connectors are not needed for
peer restart, they are no longer started when a server is
started out of place.

APAR PQ78451 is associated with SERVICE LEVEL W501000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ78451
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-09-14
Closed date 2003-09-17
Last modified date 2004-07-15

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
UQ80300 PQ91506

Modules/Macros
BBOSTMI BBOUBINF BBOWCTR BBOZ2643 BBOZ2651 BBOZ3842
BBOZ3862 H28W500J        

Publications Referenced

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

Applicable component levels
R500 PSY UQ80300    UP03/09/25 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: swg1PQ78451.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 #: PQ78451
IBM Group: Software Group
Modified date: Jul 15, 2004