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

(WS16984.02) The IJP JMS Broker and Queue Manager security
cannot be controlled dynamically depending on the security
settings for the server.

If security is required for the Queue Manager(QM) and Broker,
the security exits for the Queue Manager and the Channels
actually need to be updated manually by issuing the ALTER
command and passing CSQ4BCX3 as paramater to the security exit.
The QM and Broker security is thus independent of the server
setting for security and the process of setting it is tedious.

(WS17270)   Attempts to change the MQ JMS Provider Queue
Destination Target Client property is not saved. The property
reverts back to JMS even after saving changes.

Feature WS17270 also address:

As part of cluster creation, a replication domain is created,
but when the cluster is deleted the replication domain is not
deleted.

(WS17270.2) Deadlock in com.ibm.ejs.j2c.poolmanager.FreePool

Customer will see at least one thread in a wait state with a
traceback like this:

at com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(...)
at com.ibm.ejs.j2c.poolmanager.PoolManager.release(....)

And another thread in a wait state with a traceback like this:

at com.ibm.ejs.j2c.poolmanager.FreePool.
removeMCWrapperFromList(...)
at com.ibm.ejs.j2c.poolmanager.FreePool.returnToFreePool(...)
at com.ibm.ejs.j2c.poolmanager.PoolManager.release(....))

There could potentially be more threads in a wait state in a
FreePool method as well.
(WS17397) Listening for JMS messages is performed in the servant
region. Only one servant region can process JMS messages at a
time. The whole JMS message is processed therefore dimishing
messaging throughput. his issuue is being addressed by the
feature.
Problem conclusion
APAR PQ78456 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(WS16984.02) Support has been provided such that during
JMSServer startup the current security setting for the server
is verified. This setting is used to dynamically set
security for the Queue Manager and the Broker. When the Queue
Manager is started an ALTER command is isued to modify the
security exits for the Queue Manager channels. Later, when the
Broker is started, the security setting is honored for the
Broker. If the security setting is modified for the server,
then the server must be recycled such that the JMSServer goes
through the process already described.

(WS17270) The code was changed so that updates are saved
correctly.

Feature WS17270 also provide the following support:

Code was changed to make sure the automatically created
replication domains are deleted when the associated cluster is
deleted. Manually defined replication domains will persist until
manually deleted which is the current behaviour.

(WS17270.2) Problem resolved by adding an extra layer of Java
synchronization locking in FreePool.

(WS17397) Support has been modified to move the listening of JMS
messages to the control region. MQ functionality is avaiable to
browse messages in selected destinations and return a message
reference that is smaller than the message itself. WLM workload
classification is possible now through the use of message
selectors.

The following publication was revised as a result
of feature WS17397:
________________________________________________________________
WebSphere Application Server V5 for z/OS
Messages and Codes
GA22-7915-00
_______________________________________________________________
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:

www.ibm.com/software/webservers/appserv/zos_os390/library.html
________________________________________________________________
Chapter 1, pg. 3 new message
BBOJ0078W
Exception  exception name  loading or parsing endpoint
configuration xml file  xml filename

Explanation: An exception was found while reading the specified
xml file.
User Response: Verify the existance of the xml file and that it
is a valid document.
________________________________________________________________
Chapter 1, pg. 3 new message
BBOJ0079W
No endpoint information found in xml file  xml filename .

Explanation: No endpoint was provided in the specified xml file.
User Response: If endpoint based classification is required,
provide endpoint configuration information according to the
Inbound Classification syntax.
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912B3
Explanation: Attempt to create a WLM enclave for an inbound MDB
Request failed.
User Response: Examine the job log from the controller region
for a related BBOO0037E message.  This message will contain the
return and reason code from the WLM create enclave service
(IWMECREA).
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912B4
Explanation: Attempt to queue an MDB Request to WLM failed.
User Response: Issue D WLM,APPLENV=xxxxxx and make sure that it
is not in the STOPPED state. If it is in the STOPPED state
issue V WLM,APPLENV=xxxxxx,RESUME after fixing the problem that
caused it to get in the STOPPED state.
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912B5
Explanation: bbooboat.cpp called iwmsrcrn which failed.  Should
be seen as part of message BBOO0079E which should include the
WLM return and reason codes.
User Response: "IBM Internal Only"
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912B6
Explanation: The server is in the process of shutting down.  It
received an MDB Request and has rejected it.
User Response: "IBM Internal Only"
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912B7
Explanation: The WebSphere for z/OS  execution thread caught a
user exception while processing an outbound request. This is an
incorrect throw.  The user exception will be represented by a
system exception with this error code.
User Response: "IBM Internal Only"
Check the error log to see if the user exception was recorded
when it was thrown.  The system code throwing the user
exception should be changed to record the error and then throw
a system exception.
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912B8
Explanation: The WebSphere for z/OS control region execution
thread caught a ... while processing an inbound MDB request.
This is an incorrect throw. A system exception with this error
code is created.
User Response: "IBM Internal Only"
Check the error log to see if the error was recorded when it
was thrown.  Code should be changed to record the error and
then throw a system exception.
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912B9
Explanation: An ORB_Request was Queued to WLM, but its response
was not received in a reasonable amount of time. An ORB_Request
Registry cleanup routine, MDB Request Timed out, will cleanup
the request.
User Response: Make sure that WLM can start the target server
region (it may be in a quiesced state).  Additionally, check
that the time out value is of sufficient length.  See the
instructions in the WebSphere for z/OS Planning and
Installation Guide for setting the MDB Request time out value
via an environment variable
(control_region_mdb_request_timeout)
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912BA
Explanation: An ORB_Request was Queued to WLM, but its response
was not received in a reasonable amount of time. An ORB_Request
Registry cleanup routine, MDB Request Timed out, will cleanup
the request.
User Response: Make sure that WLM can start the target server
region (it may be in a quiesced state).  Additionally, check
that the time out value is of sufficient length.  See the
instructions in the WebSphere for z/OS Planning and
Installation Guide for setting the MDB Request time out value
via an environment variable
(control_region_mdb_request_timeout)
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912BB
Explanation: An ORB_Request was Queued to WLM, but its response
was not received in a reasonable amount of time. An ORB_Request
Registry cleanup routine, MDB Request Timed out, will cleanup
the request.
User Response: Make sure that WLM can start the target server
region (it may be in a quiesced state).  Additionally, check
that the time out value is of sufficient length.  See the
instructions in the WebSphere for z/OS Planning and
Installation Guide for setting the MDB Request time out value
via an environment variable
(control_region_mdb_request_timeout)
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912BC
Explanation: A call was made to set the ORB_Request State Flag
that indicates that cleanup responsibility for the related
ORB_Request belongs to the MDB request timed out routine, but
the State Flag Area pointer was null.
User Response: "IBM Internal Only"
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912BD
Explanation: The getJavaEnv entry point in the BBOLRT dll has
not been obtained/initialized, but should have been.
User Response: "IBM Internal Only"
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912BE
Explanation: The MDBCppUtilities::invokeOnMessageReference was
unable to drive the java "onMessageReference" routine.  The JVM
should already have been started by this point, this error
should not occur.  Check for shasta component errors.
User Response: "IBM Internal Only"
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912BF
Explanation: The getJavaEnv entry point in the BBOLRT dll has
not been obtained/initialized, but should have been.
User Response: "IBM Internal Only"
________________________________________________________________
Chapter 3, pg. 116 new message
C2C912C0
Explanation: The MDBCppUtilities::registerWithCBM was unable to
drive the java "registerWithCBM" routine.  The JVM should
already have been started by this point, this error should not
occur.  Check for shasta component errors.
User Response: "IBM Internal Only"
________________________________________________________________
Chapter 4, pg. 192 new message
Abend code: EC3 hex
Abend reason: 04130008 hex
Explanation: Control region issued a ABTERM for this server
region because the MDB Request timeout occurred. Code under
dispatch could have been in a tight loop.
User Response: If the method being dispatched was in a loop,
correct the method and try again.  If the method was
progressing, then increase the MDB Request timeout environment
variable.  Also, examine the associated Control region for any
messages that may clarify the reason for the termination of the
Server region (ex. BBOO0232)

APAR PQ78456 is associated with SERVICE LEVEL W501000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ78456
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 2003-10-29

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOCWCRD BBOCWSMP BBOIUTIL BBOLXDF BBOOASAP BBOOASC3
BBOOASGB BBOOASGE BBOOASLB BBOOASLE BBOOASS5 BBOOAS
***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 UQ80305    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: swg1PQ78456.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 #: PQ78456
IBM Group: Software Group
Modified date: Oct 29, 2003