PQ53684: 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 PQ53684 addresses various problems * * in WebSphere Application Server V4.0.1 * * for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ53684 addresses the following problems in WebSphere Application Server V4.0.1 for z/OS and OS/390: Current WebSphere Applications Server for OS/390 and z/OS only supports one visibility/classloader mode. This mode is Compatibility mode. Certain applications require Module and Application modes. When running job BBOIVP, in installation dataset BBO.SBBOJCL the success message "Java Client test compete and successful" may not be seen in the SYSPRINT ouptut of the IVP Client, even though the job has run successfully. The output of job BBO.SBBOJCL(BBOIVP) may be truncated. Not all of the output of job SBBOJCL(BBOIVP) step 3a is copied from /tmp/jcivp.out to sysprint output by job step 3b. You can look in the /tmp/jcivp.out file to see if the message "Java Client test complete and successful" was issued. When HTTP transport timeouts occur an attempt is made to close the socket, these closes could fail if there currently exists an outstanding read on that socket. In this situation the following message will be issued: BBOU0043E Function close() failed with RV=-1, RC=112, RSN=05230138, EDC5112I Resource temporarily unavailable. If this situation occurs than the socket may not get closed and the HTTP connection will be hung. When running with WS/390 Connector support a lookup of a JDBC datasource results in the corruption of the reference to the factory builder object. As a result the user will see a NullPointerExeception from within the getObjectInstance() method of the DB2JDBCResourceFactory class. There exists a need for an external variable which will allow the ability to specify a default WLM Transaction Class for the enclaves that are created to process HTTP requests that are processed by the HTTP Transport. A SIGSEGV signal occurs in a call to RUNAS::getPrincipal. The signal occurs while running a J2EE application that uses RunAs Role and also has method permissions. The SIGSEGV signal occurs because the service routine RUNAS::getPrincipal attempts to write into key 0, statically defined C++ storage during a call to EJBROLES::isCallerInRole().Problem conclusion APAR PQ53684 provides the following problem resolution: Classloader support for EJBs and Web Applications was merged into one classloader. This allowed the EJB container to pickup additional mode support supplied by the Web Container classloader. Sample part jcivp.java was updated to print the object name and not print the object IOR in output section labeled '4)'. The successful message will be included in the SYSPRINT of the BBOIVP job. Timeout processing has been changed to do a shutdown on the socket instead of a close. This allows other threads working with the socket to handle the closing of it. Processing for a lookup of a JDBC datasource has been modified so that the correct factory is used to create DB2 JDBC connections. An evironmental variable BBOC_HTTP_TRANSACTION_CLASS was created to provide the ability to have enclaves that are classified with a specified transaction class. To fix the reported SIGSEGV in method RUNAS::getPrincipal, the processing in method EJBROLES::Message() called by EJBROLES::isCallerInRole()in module bbossejb.cpp was modified to use stack storage to house the variable being filled in by RUNAS::getPrincipal. -------------------------------------------------------- APAR PQ53684 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/ WebSphere Application Server V4.0.1 for z/OS and OS/390 Assembling J2EE Applications (SA22-7836-02) will be changed as follows: Appendix A. Environment and JVM properties files Add the following new JVM property and description in the following places under topic, "JVM properties and properties files" starting on page 241: Table 15, "Where to use JVM properties" on page 242: Add property "com.ibm.ws390.server.classloadermode" with default value "1" (compatibility mode). The property is optional for J2EE server instances. Topic "Properties descriptions" on page 244: Add the following text: com.ibm.ws390.server.classloadermode=1 Specifies the visibility mode to use for the J2EE server. In other words, this JVM property value determines which classloaders can be aware of other classloaders and of the application modules to be installed in the J2EE server. WebSphere for z/OS uses several different classloaders to install different module types: modules for Enterprise beans, for Web applications, and for WebSphere for z/OS run-time classes. Valid values (visibility modes) for this property are: 0 Specifies module mode, which allows WebSphere for z/OS to use one classloader per module. Each module (JAR or WAR) has its own unique classloader. Visibility of other modules in the application is achieved only when MANIFEST classpath entries are added to a module. 1 Specifies compatibility mode, which allows compatibility with applications from previous releases of WebSphere for z/OS. In this mode, all EJB module classloaders have visibility of all other EJB module classloaders, and all Web application modules have visibility of the EJB classloaders. The search order for the EJB classloaders is deter- mined by the order in which the EJB modules were initialized. 2 Specifies application mode, which allows all classloaders in a J2EE application to have visibility of other classloaders in the same application. The search order is the order the modules are defined in the application.xml for the EAR file. 3 Specifies server mode, which allows all application classloaders on the server to have visibility of all other application classloaders in the server. The search order is the same order as when the modules were initialized into the server. WebSphere Application Server V4.0.1 for z/OS and OS/390 Messages and Diagnosis (GA22-7837-02) will be changed as follows: Chapter 12. Messages -- General (BBOJxxxx, BBOUxxxx, WRASxxxx) Add new message BBOJ0018I at the bottom of page 222: BBOJ0018I WebSphere for z/OS server "server" Visibility mode is "mode". Explanation: An informational message to indicate which Visibility mode a WebSphere for z/OS and OS/390 server is running. User Response: None, if this is the desired mode. -------------------------------------------------------- APAR PQ53684 is associated with SERVICE LEVEL W401005 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: 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 #: PQ53684
IBM Group: Software Group
Modified date: Dec 3, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.