PQ69412: INTERNAL APAR FOR WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This is an internal apar to ship fixes in V4.0.1 for apars fixed in V3.5.0 of Websphere Application Server 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: This APAR includes fixes for V3.5 APARs * * that also apply to V4.0.1 and IBM * * internal fixes for the WebSphere * * Application Server for z/OS and OS/390. * * * * Internal Defect Description: * * (84473) - * * Increment the Service level to W401408. * * * * V3.5 APARs included: * * PQ61701 * * PQ66335 * * PQ67528 * * PQ68388 * * PQ68506 * * PQ68767 * * PQ68804 * * PQ69540 * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR includes fixes for WebSphere Application Server Version 3.5 APARs that also apply to the WebSphere Application Server Version V4.0.1. 84473 - Increment the Service level to W401408. PQ61701 - The following APARs from distributed WebSphere Application Server fixpack 6 are merged into the WebSphere Application for z/OS and OS/390 code base: PQ50156 DISABLE SERVLET ONLY VALID UNTIL WEBAPP RESTARTED PQ51629 SETLOCALE() DOES NOT ADD CHARSET FIELD TO CONTENT-TYPE HEADER PQ51741 TAG INTERSPECTION HELPER IS CAUSING COMPILE TIME FOR JSPS TO TAKE TOO LONG. JSPRUNTIMELIBRARY CALLED TOO OFTEN PQ53180 REMOVE DEPENDENCY OF GETCLASSLOADER FROM HTTPJSPBASE PER SPECIFICATION PQ53274 USING .91 JSP PROCESSOR, JSP IS RECOMPILED WHEN FIRST SERVED AFTER EVERY RESTART OF WEBSPHERE APPLICATION SERVER PQ53356 ENGINE DOES NOT CORRECTLY HANDLE ALL NOTARGETFORURI EXCEPTIONS - RESTARTING THE WEB APPLICATION FIXES PROBLEM PQ53588 PERFORMANCE PROBLEM WITH CUSTOM TAGS IN JSP 1.1 ON WEBSPHERE APPLICATION SERVER VERSION 3.5.X PQ54214 CHANGE THE GENERATED JAVA CODE TO 'NOT CONVERT STATIC JSP CONTENT' TO A STRING BEFORE SENDING TO THE CLIENT PQ55236 JSP 1.0 RECOMPILES JSP EVERYTIME UNTIL APPLICATION SERVER IS RESTARTED PQ55399 JSP INCLUDES FAIL IF THE INCLUDED FILES HAVE THE SAME NAME BUT ARE LOCATED IN DIFFERENT DIRECTORIES WITH THE JSP 1.1 COMPILER PQ55686 SESSION CONFIGURATION WAS PICKED UP FROM A SESSION.XML FILE INSTEAD OF FROM THE DATABASE PQ56177 INTERNET EXPLORER DOES NOT DISPLAY 401 ERROR MSG CORRECTLY (BROWSER RECEIVES A BLANK PAGE) PQ56440 ERROR IN WAS 3.5.5: SRTSERVLERREQ ACCESS METHOS WEBSPHERE APPLICATION SERVER "POST" BUT CONTENT TYPE "APPLICATION/XXX" WAS NOT RECOGNIZED PQ56915 USING THE INVOKER TO INVOKE A SERVLET WITH TEXT AFTER THE SERVLET NAME AND SERVLET DEFINED AS INVOKER PATH RESULTS IN LOOP PQ57495 INCLUDED JSPS WITH DBCS CHARACTERS ARE NOT DISPLAYED PROPERLY. PQ66335 - Optimizations for connecting to DB2 running on OS/390 or z/OS were included in WebSphere Application Server Connection Manager. These optimizations created a dependency on classes in the DB2 JDBC driver. This can lead to a failure with other JDBC drivers and Database Management Systems. PQ67528 - WebSphere Application Server session clustering code does not handle java.io.SerializableExceptions, preventing database resources from being freed. PQ68388 - When the Connection Manager fails to make a connection to a datasource, it throws an Exception containing the message "Failed to get a connection." This Exception can be caught in the HttpServlet's service method. If a more descriptive message is received from the JDBC driver, that message is written to the ncf log. The more descriptive message is not made available to the HttpServlet. PQ68506 The JSP level 1.1 batch compile tool $was_install_root$/AppServer/bin/jsp11BatchCompile.sh generates class files from the JSP source with names which are inconsistent with those generated by WebSphere Application Server when those JSP source files have names which include special characters, such as "-" or "_". Also, both the JSP level 1.1 and level 1.0 batch compile tools $was_install_root$/AppServer/bin/jsp10BatchCompile.sh and $was_install_root$/AppServer/bin/jsp11BatchCompile.sh do not accept multiple JSP source files for compilation. PQ68767 - After the application of APAR PQ65746 found in PTF UQ69729, the JSP level 1.0 compiler incorrectly uses the Web application classpath of the the first JSP it compiles for all subsequent JSP compilations. PQ68804 - After the application of APAR PQ54575 found in PTF UQ60759, the JSP level 1.1 processor will not compile JSPs which reside in the WEB-INF directory of the Web application document root. The abstract of APAR PQ54575 states: "WebSphere v3.5 serves JSP/HTML documents to clients from WEB-INF directory in contradiction to the 2.2 spec. See section 9.4." Some customers have a different interpretation of section 9.4. These customers may want the ability to compile JSPs which reside in the WEB-INF directory of the Web application document root. PQ69540 - URL pattern to servlet code mapping behavior changed after the application of PTF UQ65839. Prior to UQ65839, a URL like /a/xxx/any.jsp with a was.conf servlet mapping of webapp.<webapp-name>.servlet.<servlet-name>.servletmapping=/a would match on /a with /xxx/any.jsp considered path information. After the application of PTF UQ65839, *.jsp is considered a better match than /a for the URL /a/xxx/any.jsp because *.jsp is a longer path than /a.Problem conclusion 84473 - The service level was changed to W401408. For the following Version 3.5 APARs, please refer to the closing text for the individual APARs for the changes that were made. PQ61701 PQ66335 PQ67528 PQ68388 PQ68506 PQ68767 PQ68804 PQ69540 APAR PQ69412 is associated with SERVICE LEVEL W401408 of WebSphere Application Server V4.0.1 for z/OS and OS/390.Temporary fix Comments **** PE03/04/07 FIX IN ERROR. SEE APAR PQ71664 FOR DESCRIPTION
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 #: PQ69412
IBM Group: Software Group
Modified date: Apr 7, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.