PQ79902: 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: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ79902 addresses various defects * * in WebSphere Application Server V5.0 * * for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ79902 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (MD18051) addNode fails when a system is configured as multi-homed tcpip stacks with ADMU0111E: Program exiting with error com.ibm.websphere.management. exception.AdminException: ADMU0036E: The Deployment Manager cannot lookup by name When a system is configured as multi-homed, it will have more than one ip address. During addNode process, the Deployment Manager pings the system that is running the addNode process and returns one ip address. Furthermore, when addNode process calls InetAddress.getByName to resolve its ip address, it might get one that is different from what the Deployment Manager returns, hence the ip address comparison will fail and we will throw an AdminException (The Deployment Manager cannot lookup by name host xxx at address xxx) (MD18052) The generated IBM HTTP Server configuration file plugin-cfg.xml does not have a CloneID field for the Server attribute when that server is not part of a cluster. This may result in the loss of HTTP session affinity to an application server, which will cause the loss of HTTP session state between HTTP requests. (MD18057) While destroying subcontext from the bind naming path a org.omg.CORBA.NO_MEMORY is received but a org.omg.CORBA.IMP_LIMIT exception was expected. (MD18066) When the http plugin initializes, it displays 0.0 as the version number. This makes it difficult to determine what level of code in running in service situations. (MD18078) The WebSphere for z/OS Customization dialog generated jobs that write to the /tmp directory will fail when /tmp directory file already exist. This applies to all dialog jobs that write to the /tmp directory. Take the job BBOWADDN for example: If user A creates and executes the job BBOWADDN, it will create two output files (bbowaddn.out and bbowaddn.err) in the /tmp directory. Assuming that user B does not have write access to user A's files, if user B creates and executes the job BBOWADDN on the same system, then user B's BBOWADDN job will fail because it can't write to user A's bbowaddn.out and bbowaddn.err files in the /tmp directory. Also, in the JOB log, there is a CC code of 512 for the (MD18079) EARExpander.sh has $JAVA_HOME/jre/bin/java the java command path, it should be $JAVA_HOME/bin/java (no jre). The following error message is received: /java/J1.3/jre/bin/java:./EARExpander.sh 15; FSUM7351 not found (MD18085) If the Daemon jobname was changed via the administrative console, then the Daemon, when started automatically by the server/dmgr, will not use the updated Daemon jobname. The 'z/OS Location Service Daemon' configuration page in the Administrative Console allows the user to change the Daemon jobname. If the Daemon jobname was changed via the Administrative Console, then the Deamon, when started automatically by the server/dmgr, will not use the updated Daemon jobname. The problem is that the value of jobname of the Daemon's start command string does not use the ${} variable substitution to get the new value of Daemon jobname. As a result, when the Daemon jobname was updated via the Administrative Console, the Daemon's start command string is referring to the old Daemon jobname. (MD18093) The messages that associated with the NodeSync completion, ADMS0003I and ADMS0006I should be printed to the z/OS Operator Console console, rather than just the debug stream. (MD18095) The host for the ORB_SSL_LISTENER_ADDRESS was not correctly defaulted to "*", but rather the hostname of the system. (MD18113) When generating the IBM HTTP Server configuration file plugin-cfg.xml, and that configuration file already exists, manual changes to the file since the previous generation are lost. This may result in the message -Fatal Error- :1:1: Content is not allowed in prolog when the shell script $server_root/bin/GenPluginCfg.sh is run to generate the configuration file. If the administration console is used to generate the file, the message BBOO0223I Problem in replacing Old Values Content is not allowed in prolog may be seen in the server log. (MD18141) The attribute javax.servlet.error.request_uri of the HttpRequest object may not contain the URI of the failing request when a Servlet Error Page is dispatched in response to a servlet error. (MD18200) Same ServerSession instance is returned to the Server Session Pool causing other requests to wait for the only ServerSession to complete its work. The Server Session Pool is filled with the same ServerSession instance. Work is only done by this instance and other requests need to wait for the instance to complete processing. (MD18218) Failure during transaction recovery of IJP resources. Mistakenly using bindings mode to create a TopicConnection (or a QueueConnection) to the IJP Queue Manager, during recovery processing. A stack trace like this may be seen (or a stack trace substituting "Queue" for "Topic"): javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'WMQX' at com.ibm.mq.jms.services.ConfigEnvironment.newException at com.ibm.mq.jms.MQConnection.createQM at com.ibm.mq.jms.MQConnection.createQMNonXA at com.ibm.mq.jms.MQTopicConnection.<init> at com.ibm.mq.jms.MQTopicConnection.<init> at com.ibm.mq.jms.MQXATopicConnection.<init> at com.ibm.mq.jms.MQXATopicConnectionFactory.createXATopicConnec at com.ibm.ejs.jms.JMSManagedTopicConnection.createConnection at com.ibm.ejs.jms.JMSManagedConnection.<init> at com.ibm.ejs.jms.JMSManagedTopicConnection.<init> at com.ibm.ejs.jms.WSJMSManagedTopicConnectionFactory.createMana at com.ibm.ejs.jms.JMSManagedSessionFactory.getManagedConnection at com.ibm.ejs.jms.JMSManagedSessionFactory.getPhysicalConnectio at com.ibm.ejs.jms.JMSManagedSession.<init> at com.ibm.ejs.jms.JMSManagedTopicSession.<init> at com.ibm.ejs.jms.JMSManagedTopicSessionFactory.createManagedSe at com.ibm.ejs.jms.JMSManagedSessionFactory.createManagedConnect at com.ibm.ejs.j2c.J2CXAResourceFactory.getXAResource at com.ibm.ws390.tx.XARecoveryAgentImpl.inflateXaResource at com.ibm.ws390.tx.XARecoveryAgentImpl.rollbackUnknownTransacti at com.ibm.ws390.tx.xarecovery._XARecoveryAgentImplBase._invoke at com.ibm.ws390.orb.CommonBridge.CORBAinvoke at com.ibm.ws390.orb.ORBEJSBridge.CORBAinvokeProblem conclusion APAR PQ79902 fixes various defects in WebSphere Application Server V5.0 for z/OS. (MD18051) Since a system may have multiple ip addresses, addNode should check for this condition. The new code will use InetAddress. Code was also modified to use getAllByName() instead of getByName() method. (MD18052) Changes are made to IBM WebSphere Application Server for z/OS and OS/390 such that when the IBM HTTP Server configuration file is generated, that file has the CloneID field in the Server attribute regardless of whether the server is part of a server cluster. (MD18057) Code is modified such a way that proper type of exception will be thrown. (MD18066) Build information from bboubinf.cpp will be displayed and logged by the http plugin during initialization. (MD18078) All dialog jobs have been updated to write to a unique file (with a time stamp) in the /tmp directory (i.e. /tmp/bbowaddn_66034.tmp). As result, the problem in question will not occur. (MD18079) EARExpander.sh was modified to use the correct path. (MD18085) Support was modified to substitute the cell-level Daemon jobname into the Daemon's node-level start command string. Dialog skeleton for the node-level variables.xml will be updated from: <entries xmi:id="VariableSubstitutionEntry_32" symbolicName= "WAS_DAEMON_daemon_start_command_args" value="JOBNAME= &DMNJNAME.,ENV=&ASCENS..&DMNNAME..&DMNINSN." description="WAS Daemon start command args"/> to this: <entries xmi:id="VariableSubstitutionEntry_32" symbolicName= "WAS_DAEMON_daemon_start_command_args" value="JOBNAME= ${WAS_DAEMON_JOBNAME},ENV=&ASCENS..&DMNNAME..&DMNINSN." description="WAS Daemon start command args"/> basically changing from: JOBNAME=&DMNJNAME. to: JOBNAME=${WAS_DAEMON_JOBNAME} (MD18093) The NodeSync messages were modified to be printed to the z/OS Operator Console rather than just the debug. (MD18095) Code was changed during server creation to correctly set the default host of ORB_SSL_LISTENER_ADDRESS. Now servers created through both the Administrative Console and through wsadmin both create properly defaulted endpoint. (MD18113) Changes are made to IBM WebSphere Application Server for z/OS and OS/390 such that when the IBM HTTP Server configuration file is generated, manual changes to the configuration file are preserved. (MD18141) Changes are made to IBM WebSphere Application Server for z/OS and OS/390 such that when an error page servlet is dispatched, method WebAppRequestDispatcher() in package com.ibm.ws.webcontainer.webapp sets the ServletRequest object's javax.servlet.error.request_uri attribute to be the URI of the failing request. (MD18200) Remove additional code that returns the ServerSession instance to the Server Session Pool. (MD18218) Transaction recovery of IJP resources was modified to use client mode when getting connection on IJP QueueManager during recovery processing. APAR PQ79902 is associated with SERVICE LEVEL W501002 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: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ79902.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 #: PQ79902
IBM Group: Software Group
Modified date: Nov 2, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.