PQ55399: JSP INCLUDES FAIL IF THE INCLUDED FILES HAVE THE SAME NAME BUT ARE LOCATED IN DIFFERENT DIRECTORIES WITH THE JSP 1.1


APAR

APAR status
Closed as program error.

Error description
Using the JSP 1.1 processor, including JSPs with the same name t
hat are located in different directories causes a error 500 with
 the following message:
Message:  Server caught unhandled exception from servlet [JSP 1.
1 Processor]:  Seen file \was\bogus\include.jsp already, maybe
this s a recursive include?!
the following message:Message: Server caught unhandled exception from servlet [JSP 1.1 Processor]: Seen file \was\bogus\include.jsp already, maybethis s a recursive include?!
Local fix
This works fine with the JSP 1.0 processor
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 3.5.4 & 3.5.5   *
*                 developers using jsp 1.1 and static          *
*                 includes.                                    *
****************************************************************
* PROBLEM DESCRIPTION: Jsp 1.1 processor fails using multiple  *
*                      static includes with same jsp file      *
*                      name.                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Using jsp 1.1 processor and developing a jsp that
contains multiple static includes, WebSphere checks
to ensure that it is not in an infinite loop caused by
repeatedly including the same file.  WebSphere was
not properly recognizing the difference between jsp files
that had the same name but in a different subdirectory.
This was causing an exception to be thrown during parsing
of the jsp page.
Problem conclusion
Code was modified to include the complete context path
of the jsp for the purpose of checking for possible infinite
loops.  Prior versions were storing only the jsp file name.
This caused WebSphere to incorrectly throw exceptions if
2 or more jsp files were named identically but were in
different subdirectories.
Temporary fix
/wasdoc0/apars/pq55399/354/pq55399_354.jar  3.5.4 version
/wasdoc0/apars/pq55399/355/pq55399_355.jar  3.5.5 version
Comments
made eFix for versions 3.5.4 and 3.5.5.
APAR information
APAR numberPQ55399
Reported component nameWAS STANDARD AI
Reported component ID5648C8300
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-12-03
Closed date2001-12-12
Last modified date2001-12-17

APAR is sysrouted FROM one or more of the following:

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


Modules/Macros
JSP
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS STANDARD AI
Fixed component ID5648C8300

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ55399
IBM Group: Software Group
Modified date: 2001-12-17