PK61357: COM.IBM.WS.JSP.JSPCOREEXCEPTION: JSPG0049E:/TESTJSP.JSP FAILED TO COMPILE.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Root cause seems to be in the following code:
  com.ibm.ws.jsp.translator.compiler.JDTCompiler$JspNameEnvironmen
  t#isPackage(compoundName, name)
  Example.
  it's Dynamic Web project with two classes in src/:
  a.b.c.D
  a.b.c.d.E
  
  and testJSP.jsp with:
  System.out.println(a.b.c.d.E.class);
  
  Opening the testJSP.jsp on WebSphere Application Server V6.1
  causes the following Error.
  a.b.c.d cannot be resolved to a type
  
  In this case, mentioned
  JspNameEnvironment#isPackage(compoundName,name)
  is called with arguments:
  
  char[][] compoundName = { {'a'}, {'b'}, {'c'} };
  char[] name = {'d'};
  
  and returns false, instead of expected true.
  

Local fix

• Deploy of the application from Adminstrative console Works.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V6.1 users *
  *                  of Java Server Pages (JSP) on Microsoft     *
  *                  Windows and iSeries.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: On case insensitive file systems, the   *
  *                      default JSP compiler will fail to       *
  *                      properly locate a package when a class  *
  *                      file with the same name exists.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The JDT name environment tries to determine if a package exists
  by using the class loader to locate a class file. It treats the
  existence of a class file as an indication that there is no
  package. On case insensitive file systems this can fail when
  package and class file names match but have different cases. As
  a result the JSP fails to compile.
  

Problem conclusion

• The JDT name environment code was modified to search for the
  directory when the file exists to ensure that there is not also
  a package with the same name. In order for this to find
  directories in a jar the jar must be created with directory
  entries.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.19.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R61W PSY

     UP