PQ98541: JSP COMPILER IS NOT HANDALING RETURN CODE FROM FILE.SETLASTMODIFY() METHOD TO DETECT IF OPERATION IS SUCCESSFUL | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When user running the WebSphere Application Server is changed by the customer, when the JSP gets modified, the JSP compiler will be unable to set the last modified date for newly compiled class due to the ownership issue of the file and setLastModify() method fails to change without giving an error. Return code from this File.setLastModify() method should be handled to print error message that setLastModify() action is failed to notify customer.Local fix NonProblem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: JSPs are getting re-compiled on each * * invocation and hence invoking the * * init() method because the timestamps * * are not being updated. The user is not * * given an indication of this failure. * **************************************************************** * RECOMMENDATION: * **************************************************************** When JSPs are compiled using the JSPBatchCompiler.sh under a userid different from the servant region userid, then all the class files are owned by the userid used to run the JSPBatchCompiler.sh in the Unix Shell environment. The same can happen when the customer switches the servant region id from one userid to another. When the JSP application is reinstalled or the JSPs have been modified, the JSPs have to be recompiled. When the server tries to recompile these JSPs it encounters a problem trying to change the timestamp on the class files owned by the different user to match the timestamps on the JSP files. We encounter this problem while trying to change the timestamp due to the restriction imposed by POSIX standard stating that in order to change the timestamp on any file you have to be the file owner. Also, you cannot change the timestamp on the file to a time in the past which is what we try to do when the new class file has been created by compiling the JSP. If the timestamp of the JSP file does not match the timestamp of the class file then the JSP will be recompiled each time it is invoked. We currently do not print the bad return code from the API that is used to change the timestamp and the user is given no indication why the JSPs are being recompiled.Problem conclusion Return code from File.setLastModify() method generates a warning message stating that the timestamp of the class file could not be changed. APAR PQ98541 is associated with SERVICE LEVEL W502023 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PQ96141 APAR is sysrouted TO one or more of the following: PQ99269 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ98541.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 #: PQ98541
IBM Group: Software Group
Modified date: Mar 1, 2005
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.