PQ48857: NEW FUNCTION | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as unreproducible in next release. Error description New functionLocal fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ48857 provides enabling support * * for performance improvements during the * * install of J2EE applications using the * * WebSphere for z/OS Administration * * Application (SM EUI) APAR PQ48856 was * * the APAR which shipped the support for * * the performance enhancements. * * * * In addition this APAR addresses various * * defects in WebSphere Application Server * * V4.0 for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ48857 provides enabling support for performance improvements during the install of J2EE applications using the WebSphere for z/OS Administration Application (SM EUI). Improvement will be noticeable during the EAR (Enterprise Archive) file processing stage of the install on the server side after the successful FTP of the EAR file which represents a J2EE application. APAR PQ48856 was the APAR which shipped the support for the performance enhancements. In addition, APAR PQ48857 addresses the following defects: Defining security settings for SendAsserted Ids for a J2EE server via the WebSphere for z/OS Administration Application is not possible without an inbound mechanism. SSL Type 1 (which means Userid/Password over SSL) needs to be enabled before any form of asserted ID. This is not correct since Accept Asserted Id only depends on the availability of Client Certificates and SendAsserted Ids depends only on there being a SSL Keyring. During resource and reference resolution through the WebSphere for z/OS Administration Application it is not possible to resolve a reference to a bean that stays within the same J2EE application (ear file) without having this reference defined as an <ejb-link>. The WebSphere for z/OS Administration Application hangs due to a out of memory condition on the work station running the Administration Application when processing large earfiles. There is no indication when this happens other than that the load operation seems to take forever. No other externals are visible expect for the hang condition. In the WebSphere for z/OS Administration Application for the (J2EE-) server definition there is a set of attributes called 'Allow Server Region Garbage Collection' and 'Garbage Collection Interval'. The term garbage collection in this context is misleading and need to be replaced by 'recycling' to meet what it is really doing. The WebSphere for z/OS Administration Application export server function can not be used on any other conversation but the active one. It would be very helpful, if servers could be exported also from conversations that have already been replaced. Once a J2EE application had been successfully loaded into the WebSphere for z/OS Administration Application and all references have been resolved there is the chance to save the resolved application to a new copy of the ear file and later on directly load the resolved application to avoid redoing all the manual steps again. When a resolved J2EE application is loaded to the Administration Application, it is possible that it contains references to non existing resources or other beans. This is not detected by the Administration Application and it is possible to install this invalid application. During resource and reference resolution through the WebSphere for z/OS Administration Application there is the possibility that a variety of possible target beans or resources is offered in the drop down listbox that are all listed under the same name This is because the bean names are displayed in the list, and there is the possibility to have the same bean installed in multiple applications on multiple servers. But regardless which target is selected by the user in the list, always the first one will be actually taken. Some J2EE application development tools do not automatically generate default transaction attributes for all methods. When such J2EE applications are being installed to WAS/390 this can lead to unpredicted results and therefore needs to be prevented. A possible problem might be a DB2 deadlock situation. When the same J2EE application is installed 2 times in a row through the WebSphere for z/OS Administration Application in many cases a nullpointer exception occurs. In that case the Administration Application needs to be stopped and restarted before being able to install that J2EE application a second time.Problem conclusion Temporary fix Comments APAR PQ48857 provides enabling support for performance improvements during the install of J2EE applications using the WebSphere for z/OS Administration Application. Existing steps for installing/deploying a J2EE applications do not change as a result of this support. APAR PQ48856 was the APAR which shipped the support for the performance enhancements. In addition, APAR PQ48857 provides the following defect resolution: Using the WebSphere for z/OS Administration Application, SendAsserted Ids can now be enabled as soon as a SSL Keyring has been entered. Code has been added to the WebSphere for z/OS Administration Application to enable the resolution of a bean reference within the same J2EE application. The WebSphere for z/OS Administration Application has been enabled to get as much memory as possible for the Java Virtual Machine, so that it should rarely run out of memory now. In cases where the total amount of memory is still not sufficient an according error message is displayed now. In the WebSphere for z/OS Administration Application the attributes on (J2EE-)Server have been renamed to 'Allow server region recycling' and 'Server recycling interval'. The helps have been updated accordingly. The WebSphere for z/OS Administration Application export server function has been enabled on conversations in state replaced as well. The WebSphere for z/OS Administration Application is now performing a consistency check for resolved J2EE application and removes all invalid references by issuing an according warning message. There was a problem in the code, where the WebSphere for z/OS Administration Application could not distinguish between different list entries that have the same name. So although there were actually different target beans listed under the same name, the WebSphere for z/OS Administration Application always found the first one in the list under this name and took it as the actual one. The problem was corrected by using a different lookup strategy. A check is now implemented in the WebSphere for z/OS Administration Application that will detect the situation where either entity beans or session beans with container managed transaction are missing transaction attributes for any method. Such J2EE applications cannot be installed through the Administration Application any more. Message BBON0885 will be issued in the case of this install failure. The nullpointer exception is caused by an error on the classes that are used to read and write deployment descriptor data from the J2EE application ear files. Those classes have been replaced by a newer version that does not have this problem. The following publications were revised as a result of APAR PQ48857: ________________________________________________________________ WebSphere Application Server V4.0 for z/OS and OS/390 Messages and Diagnosis GA22-7837-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: http://www.ibm.com/software/webservers/appserv/ ________________________________________________________________ Chapter 9, pg. 143 (new message) BBON1141I The following activation steps already succeeded: Explanation: The activation of a conversation failed but some changes might have already taken effect. This message will be followed by one or more of the messages BBON1142I, BBON1143I, BBON1144I or BBON1145I. They will indicate which steps towards a successful activation are already complete. ________________________________________________________________ Chapter 9, pg. 143 (new message) BBON1142I Environment files for conversation conversation-name are successfully written. Explanation: The environment changes will take effect for every server that gets recycled or started from now on. ________________________________________________________________ Chapter 9, pg. 143 (new message) BBON1143I Conversation conversation-name is now the active conversation. Explanation: The system considers the conversation as active even though the activation process was not completed. ________________________________________________________________ Chapter 9, pg. 143 (new message) BBON1144I Homes successfully queued for registration. Explanation: The next time a server recycles or starts he will do the necessary home registration work. ________________________________________________________________ Chapter 9, pg. 143 (new message) BBON1145I Servers recycled for conversation conversation-name. Explanation: All changes for conversation conversation-name are in effect now. ________________________________________________________________ Chapter 9, pg. 167 (new message) BBON3197E UserID useridvalue not authorized for administration Explanation: This error occurs when the REXX script is executed from a non-admin userid. User Response: Verify that the userid is authorized for administration. ________________________________________________________________ The following new and changed messages are documented in the help system for the Administration and Operations applications (SM EUI). These messages will also be documented in a future edition of WebSphere for z/OS: Messages and Diagnosis. BBON0193 It is recommended to upgrade Systems Management Client application to version {0}. ("version" was formerly named "level") BBON0194 It is required to upgrade Systems Management Client application to version {0}, server disconnected. ("version" was formerly named "level") BBON0195 Unable to obtain working dir for ear file transfer. Using /tmp instead. Reason: {0} (new message) BBON0462 Unable to import server {0}. (formerly included the following text: ".... from input directory {1}") BBON0473 Unable to save EAR file {0}. ({1}). (new message) BBON0884 Application {0} does not contain a valid ejb module. (new message) BBON0885 Application does not contain transaction attributes for methods in EJB <{0}> in module <{1}>. Use Application Assembly Tool to add them. (new message) BBON0886 The application contains references to non existent resources. References have been reset. (new message) BBON0887 The application contains references to non existent Enterprise Java Beans. References have been reset. (new message) BBON0888 Ear file validation failed: {0}. (new message) BBON1062 Unable to export configuration. (formerly included the following text: "...to output file {1}") BBON1084 The server configuration file {0} could not be opened. (changed from "File {0} could not be opened for importing server {1}") BBON1087 Initialization of XML utility environment failed. (changed from "Initialization of Ism_ConfigTree failed") BBON1088 The XML parser detected errors in the server configuration file {0}. (changed from "Import of configuration data into the Ism_ConfigTree object failed.") BBON1113 Unable to obtain administrator export directory from server. (new message) BBON1114 Unable to obtain administrator working directory from server. (new message) BBON1122 Write to HFS failed for file {0}. (new message) BBON1123 The name of the export file could not be assembled. (new message) BBON1124 The creation of symbolic link {0} failed. (new message) BBON1125 The removal of symbolic link {0} failed. (new message) BBON1126 An invalid directory name {0} was specified. (new message) BBON1135 The cleanup of the HFS directory {0} was not successful. (new message) BBON1136 The cleanup of file or directory {0} was not successful. (new message) BBON1141 The following activation steps already succeeded: (new message) BBON1142 Environment files for conversation {0} are successfully written.(new message) BBON1143 Conversation {0} is now the active conversation. (new message) BBON1144 Homes successfully queued for registration. (new message) BBON1145 Servers recycled for conversation {0}. (new message) ________________________________________________________________ WebSphere Application Server V4.0 for z/OS and OS/390 System Management User Interface SA22-7838-00 ________________________________________________________________ Chapter 3, pg. 20 (Icons for conversations) The conversation is an image in the state "ready for activate" or "activate in progress". In the state "activate in progress" the conversation is active, even if the activation process failed. The instructions are completed. You cannot delete this object. ________________________________________________________________ Chapter 3, pg. 25 (Activate an image) Note: Even if the activation process fails, the new image might be the active conversation! Open the message log and look whether you find the message "Conversation conversation-name is now the active conversation". ________________________________________________________________ Chapter 3, pg. 26 (Activate an image) Note: Even if the activation process fails, the new environment variables might be written to HFS. APAR PQ48857 is associated with SERVICE LEVEL W400031 of WebSphere Application Server V4.0 for z/OS and OS/390.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ90027 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ48857
IBM Group: Software Group
Modified date: Oct 2, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.