PQ59164: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V4.0.1 for z/OS and OS/390.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ59164 addresses various problems * * in WebSphere Application Server V4.0.1 * * z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ59164 addresses the following problems in WebSphere Application Server V4.0.1 for z/OS and OS/390: (MD12568) Currently, after an application family is deleted, its associated query metadata is not deleted when the conversation is activated. This results in orphaned records in the customer's System Management (SM) database. Delete processing needs to be fixed to (1) delete associated query metadata when an application family is deleted, and (2) mark all servers referencing a deleted resource instance as changed. When an MOFW application family is deleted, the query metadata (table aliases, mapped type DDLs, and related homes) associated with this application family is marked as changed rather than deleted. This metadata does not get deleted from the database when the conversation is activated. When an LRM instance or J2EE resource instance is deleted, the server group(s) to which this resource belongs needs to be marked as changed so the appropriate server instances will be recycled when the conversation is activated. (MD12759) The Java environment variable "IBM_JAVA_OPTIONS" takes a list of startup options for the JVM. These startup options will overide our Server Region startup options, if set. Such an overriding behavior of WebSphere environment variables should not be allowed. (MD12893) If class EJBROLE is not active during run time, the check for isCallerInRole always returns FALSE. This EJB Role checking behavior should be modified to match Websphere Application Server Advanced Edition, which will return TRUE in this situation. (MD12969) Security information regarding how many pushes were being performed gets lost when calling an EJB method from another EJB method. This can result in extra pops on the security stack, in addition to lost security information as to which identity is calling which methods. (1)Users may be denied access to methods to which they should have access to in nested EJB method calls. Exceptions that can be reported for this scenario are: java.rmi.RemoteException java.rmi.AccessException com.ibm.websphere.csi.CSIAccessException org.omg.CORBA.NO_PERMISION (2) Users may also gain access to methods they should not have access to in nested EJB method calls. This scenario does no produce any exceptions. (3) Another external symptom sometimes occurs when the problem is occurring when no exceptions are thrown. This JRAS trace entry is produced in certain situations when security information is lost in nested EJB method calls: Trace: <date> <time> 01 t=<thread id> c=1.6 key=P8 (13007002 FunctionName: com.ibm.ws390.sec.WS390ThreadSecurity SourceId: com.ibm.ws390.sec.WS390ThreadSecurity Category: DEBUG ExtendedMessage: callerSubject Stack is empty in pop (MD13103) HTTP enclaves don't get classified to the WLM service class specified. Transaction class is incorrectly passed on the WLM Classify macro (IWMCLSFY) used in creation of WLM Enclaves for queuing work from Control Regions to Server Regions. The transaction class is passed to bboowecr.plx for use on the TRXCLASS parm of IWMCLSFY. However, when a local variable, TransactionClass, is primed for the IWMCLSFY call, it uses the User Id parm value instead of the new Transaction Class parm value. (MD13154) Potential ABEND0C4/ABENDS0C4 using ORB tracing (TRACEDETAIL=4): The customer may experience an ABEND0C4 resulting from reference to uninitialized storage in Trace 0404801E. (MD13287) Error BBON0112E occurs when the System Management End User Interface (Administration and Operations applications), also known as the SM EUI, tries to load the J2EE Resource NLS properties file on the server for a J2EE Resource type. The NLS properties file may not be present because the J2EE Resource provider does not have NLS support for the J2EE Resource type. When the loading of the NLS properties files fails, the default is to take the English text out of the J2EE Resource type XML file, but this was not stated in message BBON0112E since it is generally used when loading java resource files. (MD13305) Server Regions receive a SystemException CORBA::NO_PERMISSION with minor code C9C2202C. A Server region thread was under dispatch for a request originating from the Control region of the same server. This particular flow was the "endOfJNDIRegistration" method on the "SMO" class. This method is a one-way request from the control region into the same server's server region. In this path the, "identity" field of the SecurityExecutionEnvData (SEE) was blank. It should have had the server's identity. Under dispatch of the "endOfJNDIRegistration" method, an outbound request to naming was made. The identity flowed with this outbound request was blank. This resulted in a SystemException with NO_PERMISSION and minor code of C9C2202C. ( PQ58665) The System Management End User Interface (Administration and Operations applications), also known as the SM EUI, does not allow sysplexes with a sysplex name that starts with a numeric character to be saved after modifying. Error BBON0854E is being shown: {propertyName} value must start with an alphabetic character. Sysplex name can have a number as the first character also.Problem conclusion APAR PQ59164 provides the following problem resolution: (MD12568) The markForDeletion method in bbomtplt.cpp that handles deletion of application families was modified to mark all associated query metadata of the application family as deleted. The markForDeletion methods that handle LRM instances and J2EE resource instances were modified to mark all server groups associated with the resource instance as changed. (MD12759) A new WebSphere environment variable "WAS_JAVA_OPTIONS" will be used to control the JVM env variable "IBM_JAVA_OPTIONS". "WAS_JAVA_OPTIONS" will only accept a list of JVM startup options and, upon being set, will set the "IBM_JAVA_OPTIONS" to these options. The "WAS_JAVA_OPTIONS" option in the 4.01 release is intended to be used by only service for debugging purposes. (MD12893) The checking for method permission and for isCallerInRole will now return TRUE if the class EJBROLE is not active during run time, matching the behavior of Websphere Application Server Advanced Edition. (MD12969) Support has been added to properly keep track of pushes performed on the stack with respect to EJB methods called within EJB methods. (MD13103) Code has been updated in bboowecr.plx to use the supplied transaction class string on the WLM Classify (IWMCLSFY). (MD13154)Trace Entry in module bbooejsb method ORBEJSBridge::parse_output_message() was modified to correctly trace the message buffer. (MD13287) Support has been added to issue a new informational message, BBON0517I, for source NLS properties file load failures. This message states: Unable to load national language properties file {0} for J2EE Resource Instance, reason: {1}. By default, English is used. (MD13305) Code has been modified in the request path starting from a control region and targeted to its own server region. These changes will set the "identity" field of the SEE to the appropriate identity. ( PQ58665) Support has been modified to allow a numeric characters as the first character for a sysplex name to be specified in the SM EUI. The following publications were revised as a result of APAR PQ59164: ________________________________________________________________ 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: http://www.ibm.com/software/webservers/appserv/ ________________________________________________________________ ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Messages and Diagnosis GA22-7837-02 ________________________________________________________________ Chapter 9, pg. 113 (new message) BBON0517I Unable to load national language properties file file name for J2EE Resource Instance, reason: reason. By default, English is used. Explanation: The SMEUI uses the National Language Support (NLS) properties file, file prefix.properties, of a J2EE resource to determine in what language to display the J2EE resource instance. The System Management server could not load the NLS properties file for the J2EE resource instance. The SMEUI displays the J2EE resource instance in the default English language. User Response: Review the following reason and follow the steps to correct the problem: File not found on host: Insure the following: The NLS properties file exists for a J2EE resource type. If the file does not exist, the resource provider may not have NLS support available for the J2EE resource type. The NLS properties file is located in the same directory as the J2EE Resource template xml file. The file and path permissions for the NLS properties file allow the System Management server to access the NLS properties file. _______________________________________________________________ Chapter 9, pg. 147 (changed) BBON1104E Could not move source-file to destination-file. Explanation: The Prepare for cold start action or Activate action failed, because one of the configuration data files could not be moved. User Response: Make sure that the files in the following paths allow write access: "CBCONFIG/Sysplex_name/conversations/current" and "CBCONFIG/controlinfo/envfile/Sysplex_name/ServerInstance_name/" where - CBCONFIG is the path that you specified in the environment variable CBCONFIG. The default for CBCONFIG is /WebSphere390/CB390 Sysplex_name is the name of any sysplex ServerInstance_name is the name of any server instance that belongs to the sysplex ________________________________________________________________ ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Assembling J2EE Applications (SA22-7836-02) will be changed as follows: Chapter 4. A closer look at the J2EE server Subtopic "Summary of requirements for using security roles and identities" In Table 4 on page 38, change the configuration tasks for "isCallerInRole method" to the following: 1. Define EJBROLE classes and profiles using RACF 2. (Optional) Define GEJBROLE classes Note: During run-time, the isCallerInRole method always returns true if the EJBROLE class has not been activated. In Table 4 on page 38, change the configuration tasks for "Security roles and method permissions" to the following: 1. Define EJBROLE classes and profiles using RACF 2. (Optional) Define GEJBROLE classes Note: During run-time, method permission checks always return true if the EJBROLE class has not been activated. ________________________________________________________________ ________________________________________________________________ Document Name: WebSphere Application Server V4.0.1 for z/OS and OS/390: Installation and Customization Document Number: GA22-7834-02 In "Appendix A. Environment files," add the following: o In Table 42, add a row for WAS_JAVA_OPTIONS. There is no default, and the environment variables are optional for all servers. o Also in the Appendix, add the following environment variable description: WAS_JAVA_OPTIONS=-option1 -option2 -option3 Should be used only under the direction of IBM support. The default is null. APAR PQ59164 is associated with SERVICE LEVEL W401036 of WebSphere Application Server V4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ64634 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ59164
IBM Group: Software Group
Modified date: May 2, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.