APAR status |
Closed as program error.
| Error description
When customer turns on JVM debug flag (under Application Server,
Debug tab) the JSPs do not compile. Local fix
Turn off JVM debug. Problem summary
After enabling the debug option under the Application Server's
Debug tab, file not found exception will be thrown. This
occurs when trying to access a simple JSP. The JSP will get
served properly on the browser, but the exception will show up
in the default_server stderr log. Problem conclusion
ClassLineModifier() and prepareClassFileForDebug() methods are
called twice from compile() method. The first call is made
even before the class file of the Jsp is renamed and moved
to the required directory and the second call is made after
renaming is done and moved to the correct directory. Hence
the Initial calls to ClassLIneModifier() and
prepareClassFileForDebug() are commented out from compile()
method so that FileNotFoundException will not occur.
This problem has been corrected by a change in:
com\sun\jsp\compiler\Main.java This problem has been corrected by a change in:com\sun\jsp\compiler\Main.java Temporary fixComments
APAR information | APAR number | PQ46693 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-03-05 | Closed date | 2001-07-06 | Last modified date | 2001-07-06 |
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 APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|