PQ67354: JSPBATCHCOMPILER FAILS IF EAR INSTALLED IN DIFFERENT DIR ON HORIZONTAL CLONE | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description There exist a condition when using horizontal clones in a Server Group that will cause the jspBatchCompiler to fail. If the directory location for the EAR is different on the 2 nodes the jspBatchCompiler will fail on one of the nodes with a NullPointerException. Stack trace looks like the following on the base WebSphere 4.0.3 installation: java.lang.NullPointerException at org.apache.jasper.compiler.ibmtools.AEBatchC.compileDir (AEBatchC.java:373) at org.apache.jasper.compiler.ibmtools.AEBatchC. buildTempDirectoryAndCompile(AEBatchC.java:324) at org.apache.jasper.compiler.ibmtools.AEBatchC. compileEnterpriseApp(AEBatchC.java:189) at org.apache.jasper.compiler.ibmtools.AEBatchC.compile (AEBatchC.java:155) at org.apache.jasper.compiler.ibmtools.JspBatchCompiler.compile (JspBatchCompiler.java:17) at org.apache.jasper.compiler.ibmtools.JspBatchCompiler.main (JspBatchCompiler.java:28) at java.lang.reflect.Method.invoke(Native Method) at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158) This directory can be different for multiple reasons. It can be different if the WebSphere installation is different from one machine. An example would be where one node1 has installed WebSphere in /opt/WebSphere/AE and node2 has installed WebSphere in /opt/WebSphere/AppServer. Then the EAR would be installed as follows: node1: /opt/WebSphere/AE/installedApps/earFileName node2: /opt/WebSphere/AppServer/installedApps/earFileName. Runtime of this example would work ok but the jspBatchComple will not work on one of the nodes. Another example would exist if after installing the EAR, the EAR's install directory is changed as with WebSphere Commerence Suite. The workaround for this situation is to have both node's clones have identical install names for WebSphere and the EAR file.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users * * who batch compile JSPs deployed in a * * horizontally cloned environment. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere cannot properly locate * * the installed ear directory for JSPs * * installed in a server group * * environment. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere throws a NullPointerException when attempting to compile a directory when an ear file is deployed in a horizontally cloned environment. The JSPBatchCompiler was unable to match the correct installation directory for the node that was being compiled. If the directory structure was the same on both machines, this operation was performed successfullyProblem conclusion WebSphere was incorrectly matching the primary node on which the ear was installed on instead of the requested node's install directory when batch compiling. At compile time, the batch compile will request the information from the node that is being compiled to obtain the correct install directory information.Temporary fix //wasdoc0/apars/pq65734/<version>Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ67354
IBM Group: Software Group
Modified date: Nov 6, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.