PQ73259: JSP Compile errors | |||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||
APAR status Closed as documentation error. Error description WAS 4.0.4 JSP Batch compiler does not place files on remote machine. Customer is able to deploy their applications when they don't use AAT, but set module visibility to APPLICATION. This bypasses the need to have a correctly completed manifest.mf in order to find needed classes. However, the extention to J2EE standards that we call Module Visibility was not added to the JSP Batch Compiler. As a result, when batch compiling and deploying, classdefnotfound errors occur. Architecturally, the extensions to J2EE we provide in the runtime environment were not intended to be added to the command line tools. Customer is frustrated that we made it easy for them to avoid updating the manifest.mf when we use WebSphere one way, but not another. Documentation does not identify this limitation when using command line tools.Local fix Manually copy files to the remote machine. Another option is to use AAT to update the manifest.mf with the appropriate classpath prior to invoking JSP Batch CompilerProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server customers * * using the JSP Batch Compiler tool with both * * a local and remote node. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server, Version * * 4.0.4 JSP Batch Compiler does not * * place files on remote machine. * **************************************************************** * RECOMMENDATION: * **************************************************************** In a server group environment, the repository is shared with multiple instances of a WAR. This means that all the files can exist on one machine (single node - vertical cloning) or on many machines (multiple nodes - horizontal cloning). The JSPBatchCompiler tool uses the nodeName option to retrieve configuration information for that node. If the nodeName is a remote machine, the JSPBatchCompiler tool outputs the compiled classes to the localNode, not the remoteNode. Documentation does not state that the JSPBatchCompiler tool outputs the compiled classes to the localNode, not the remoteNode and that the customer will need to copy the compiled content to the remoteNode. The InfoCenter will be updated to document that the customer needs to copy the compiled content to the remote machine.Problem conclusion Close this APAR as a documentation change. This update will appear on the library page for Version 4.0.6 after 05/30/2003.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 > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ73259
IBM Group: Software Group
Modified date: Jun 3, 2004
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.