PQ81154: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V5.0 FOR Z/OS. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() 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: r * * r * * r * * r * * r * * r * * All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ81154 addresses various defects * * in WebSphere Application Server V5.0 * * for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ81154 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (MD18533) PostInstaller log for W501000 contains the following messages: WASX7011E: Cannot find file "MD17790_apply.jacl" could not update security.xml with new SSL Keyring during Postinstaller processing. (MD18547) A NullPointerException can result when the IBM Http Server plugin configuration file generation script GenPluginCfg.sh is invoked with the -server.name xxxx parameter for a server which is not defined. This causes the message PLGC0033E: Runtime exception caught while generating plugin configuration: java.lang.NullPointerException to be displayed in response to GenPluginCfg.sh invocation. The IBM Http Server plugin configuration file plugin-cfg.xml generation script GenPluginCfg.sh can generate a NullPointerException when invoked with the -server.name x parameter if the server x does not exist in the configuration. This results in the following being displayed in the OMVS session: /WebSphere/V5R0M0/AppServer/bin>./GenPluginCfg.sh -server.name x IBM WebSphere Application Server, Release 5.0 WebSphere Plugin Configuration Generator Copyright IBM Corp., 1997-2002 PLGC0008I: Generating single server plugin configuration file for cell SY1, node SY1, server x. PLGC0033E: Runtime exception caught while generating plugin configuration: java.lang.NullPointerException This occured because the addServer() method of class com.ibm.websphere.plugincfg.generator.ConfigurationParser was attempting to generate the series of messages PLGC0032E: Exception caught while generating plugin configuration: /WebSphere/V5R0M0/DeploymentManager/config/cells /PLEX1Network/nodes/PLEX1Manager/servers/x /server.xml (EDC5129I No such file or directory.) PLGC0004E: An exception occurred while running GenPluginCfg. To see exception trace information, rerun GenPluginCfg with the -debug option set to yes. using an uninitialized nls message object. (MD18548) Unable to set a value in the cell-persistant namespace, and access it from another server. The following scenerio would fail: 1) get a initialContext from SY1/server1. 2) Lookup the cell-persistent root context through "cell/persistent" 3) createSubcontext under the cell-persistent, such as: "ctxTime0" 4) get another initialContext from SY2/server2 5) lookup the cell-persistent root context through "cell/persistent" from SY2/server2 InitialContext 6) Use the SY2/server2 "cell/persistent" root context to lookup "ctxTime0" but "ctxTime0" has never reached there. Additionally: The NameServerPrivate mbean was not reachable by the JMX framework, a simple test is to perform the following command in wsadmin scripting. (jacl command) $AdminControl queryNames WebSphere:type=NameServerPrivate,* The only mbeans that were returned where those residing in the nodeagent. (MD18573) When configured to use HTTPSession Memory-to-Memory Replication, SegmentLengthExceptions may be observed. When configured to use HTTP Session Memory-to-Memory Replication, SegmentLengthExceptions may occur because the replication client and replication broker have been initialized with different segment size values. The following execption and stack trace are observed in the log when this error occurs: BBOO0220E DRSW0008E: Exception is: com.ibm.disthub.impl.jms.JMSWrappedException: at com.ibm.disthub.impl.jms.ExceptionDispatchThread.dispatch (ExceptionDispatchThread.java:126) at com.ibm.disthub.impl.util.SafeDispatchQueue.run (SafeDispatchQueue.java:156) at java.lang.Thread.run(Thread.java:513) ---- Begin backtrace for Nested Throwables com.ibm.disthub.impl.util.SegmentLengthException: at com.ibm.disthub.impl.util.SimplestSegmentReader.get (SimplestSegmentReader.java:108) at com.ibm.disthub.impl.client.ConnectorImpl.receive (ConnectorImpl.java:770) at com.ibm.disthub.impl.client.ConnectorImpl.run (ConnectorImpl.java:724) at java.lang.Thread.run(Thread.java:513) com.ibm.ws.drs.JMSSessPoolWrapper BBOO0220E DRSW0009E: Linked exception is: com.ibm.disthub.impl.util.SegmentLengthException: at com.ibm.disthub.impl.util.SimplestSegmentReader.get (SimplestSegmentReader.java:108) at com.ibm.disthub.impl.client.ConnectorImpl.receive (ConnectorImpl.java:770) at com.ibm.disthub.impl.client.ConnectorImpl.run (ConnectorImpl.java:724) at java.lang.Thread.run(Thread.java:513) com.ibm.ws.drs.JMSSessPoolWrapper (MD18587) The messages ADMS0003I or ADMS0016I appear everytime a sync is run, even if no changes are made. This behavior should be changed to only output to the MVS Operator Console if documents have been changed, and to divert to the SYSLOG if it is just normal confirmation of the Auto Sync checking the state of the Node. (MD18598) A cluster member created through wsadmin scripting, will not start. This message appears on the MVS Operator Console: BBOM0053E FOR ENVIRONMENT VARIABLE server_generic_short_name A value must be assigned. This problem occurs when the ServerCluster is created in the following manner: Using the following jacl as an example: set clust $AdminConfig create ServerCluster $cell {{name Sample}} At this point you have an empty ServerCluster with no Cluster Members defined. The following command is then issued, again using the following jacl as an example: set clustermem $AdminConfig createClusterMember $clust $node {{memberName samplemem}} This server is not created properly as it uses the default template and does not have the clusterName attribute set. Clusters created through the Administrative Console, or using the wsadmin convertToCluster command are not affected. (MD18607) Assertion failure in bbottmcr.cpp for controlRep_p != NULL, followed by controller region termination with reason code C9C20020. A previous request executing on a control region thread did not correctly disassociate the transaction from the thread when the request ended. When a new request was received on the same thread, the transaction service attempted to find the information related to the previous transaction, but failed because the transaction had already been completed. (MD18615) For MDB processing, maximum number of uncommitted messages in a unit of work is reached causing messages not to be delivered. The message, MQJE001: Completion Code 2, Reason 2024 is an indication of this problem. After a message is consumed in a ServerSession, the message is not acknowledged. This causes an accumulation of uncommitted messages. The queue manager has the MAXUMSGS property set with the maximum amount of messages until a syncpoint is reached. When this maximum is reached, an MQException is thrown along with the message, MQJE001: Completion Code 2, Reason 2024. The ServerSession can no longer deliver messages to the MDB. (MD18619) -104 SQL Exception received when attempting to discover tModel in UDDI. "A serious technical error has occurred" and -104 SQL thrown when attempting to discover entries within UDDI. (MD18666) Invoking wsadmin command "$AdminControl getAttribute_jmx server" on the Application MBean failed to return the server name of the deployed application wsadmin came back with blank output. The Application MBean looks up the Server MBean in the Servant Region. However, there is no Server MBean registered in the Servant Region. The Application MBean needs to look up the name in the controller region instead. (MD18679) When running BBOWR2FA and BBOWR2FD install/configuration jobs, the following message occurs when the PATH environment variable does not include the java/J1.3/bin directory: keytool: /WebSphere/V5R0M0/AppServer /bin/bbowr2fa.sh 22: FSUM7351 not found there was no '.' placed in front of the setupCmdLine.sh call on line 17 of the script, so the environment in bbowr2fa.sh and bbowr2fd.sh was not updated with the commands in setupCmdLine.sh (MD18711) The WAS HOME value that appears in the "Federate Base Application Server node" option on the dialog could be wrong and the dialog does not allow that field to be changed. Currently, when the user runs the "Federate Base Application Server node" option in the customization dialog, it requires the user to load the savecfg that was saved from the "Configure Deployment Manager node" option. However, the Base Appserver's WAS HOME that appears on the panel for the "Federate Base Application Server Node" is not necessary the correct WAS HOME. For example, if the user configures Base Application Server A, and then configures the Deployment Manager (using the savecfg from the Base Application Server A configuration). The user then saves the Deployment Manager's configuration variables. The Deployment Manager's savecfg will have both Base Application Server A's variables and Deployment Manger's variables. Now, the user configures Base Application Server B. If the user wants to federate Base Appserver B into the Deployment Manager, following the dialog instructions, they would load the Deployment Manager's savecfg. But the Base AppServer information stored in Deployment Manager's savecfg is Base Application Server A's and not Base Application Server B's. So, the WAS HOME that appears on the panel is not Base Application Server B's and is wrong. The problem is that on the "Federate Base Application Server node" panel, the WAS HOME value is not configurable. If we allow the WAS HOME value to be configurable, then the user can simply type in the WAS HOME for Base Application Server B. And then the generated jobs will have the correct WAS HOME in it.Problem conclusion APAR PQ81154 fixes various defects in WebSphere Application Server V5.0 for z/OS. (MD18533) MD17790_apply.jacl and MD17790_backout.jacl are in the wrong codepage. New parts called MD18076_apply.jacl and MD18076_backout.jacl were shipped to fix this problem. MD17790 post install processing is now done by MD18076. MD17790.sh is changed to be a NOOP (MD18547) Changes are made to IBM WebSphere Application Server for z/OS such that messages are output correctly. (MD18548) In order to update the cell-persistant name space, the NameServerPrivate mbean was needed Any searches for the mbean were looking into the wrong region. The search looked in the Servant Region of an Application Server, rather than the Controller Region were the mbean resides. (MD18573) The problem is caused by a difference in the initialization values for segment size in the client and in the broker. The different initialization values have been corrected such that both the client and the broker are intialized with the same value for segment size. (MD18587) Message logic was changed to only appear on the MVS Operator Console when a document has been changed. The message will always appear in the SYSLOG, when appropriate. (MD18598) Code was put in place to ensure the clusterName attribute is set correctly in all types of Server creation: clustered and non-clustered. (MD18607) Code was changed to ensure the transaction was disassociated as appropriate during sending_reply. **************************************************************** Defect MD18607, 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 3, pg. 136 (new minor code) Message identifier - text - C9C2194A Explanation: Non-existent transaction detected in the received_request method. User Response: Check the message and error logs for information relating to a transaction timeout as a timeout is the most likely cause of this error. If the problem persists, contact the IBM Support Center. (MD18615) Support has been modified to acknowledge messages after they have been consumed from a ServerSession only if the acknowledgement mode is not CLIENT_ACKNOWLEDGE and the session is not transacted. This will cause the underlying queue manager to commit. (MD18619) version 2.0.4 of UDDI does not properly support DB2/390 as a backing store. It makes use of DB2/UDB syntax that is not supported. UDDI Persistence layer modified to generate SQL that is also supported on DB2/390. (MD18666) The Application MBean code has been changed to lookup the ServerMBean in the control region instead. (MD18679) Added a '.' in front of setupCmdLine.sh (MD18711) To fix the problem, the customization dialog needs to allow the WAS HOME field on the "Federate Base Application Server node" panel (panel name: BBOWPA11) to be configurable. APAR PQ81154 is associated with SERVICE LEVEL W502000 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ82905 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ81154.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 #: PQ81154
IBM Group: Software Group
Modified date: Jan 3, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.