PK72039: JSPBATCHCOMPILER SKIPS COMPILING JSPS IN DIRECTORY AFTER COMPILE ERROR

Fixes are available

APAR status

Closed as program error.

Error description

When running JspBatchCompiler on WebSphere Application Server
V6.0.2, if one of the JavaServer Pages (JSP) files in the
current direcotory encounters a compilation error then all
remaining JSPs in that directory will be skipped for compiling
and the JspBatchCompiler will continue with the next directory

Local fix

```
runtime compile
```

Problem summary

****************************************************************
* USERS AFFECTED:  All WebSphere Application Server Version    *
*                  6.0.2, 6.1 and 7.0 users of the             *
*                  JspBatchCompiler.                           *
****************************************************************
* PROBLEM DESCRIPTION: The JspBatchCompiler does not           *
*                      continue compiling files in a           *
*                      directory after a compilation error     *
*                      occurs.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If an error occurs when using the JspBatchCompiler to compile
multiple JavaServer Pages (JSP) in a directory, an attempt to
compile subsequent JSPs in that directory will not be made.
For example:
If an application has a directory with four independent JSP
files in it named:
test1.jsp
test2.jsp
test3.jsp
test4.jsp
While running the JspBatchCompiler, a compile error occurring
in test2.jsp would result in test3.jsp and test4.jsp not
getting compiled.  However, test1.jsp would be compiled since
it was compiled before the attempt to compile test2.jsp was
made.

Problem conclusion

The JspBatchCompiler code was modified to continue to compile
subsequent JSP files in a directory after a compilation
failure.
To enable this new behavior, the following JspBatchCompiler
option must be set to true:
compileAfterFailure
Example:
JspBatchCompiler.bat -war.path C:/TestApp.war
-compileAfterFailure true
Please note that this option is only applicable when using the
JDK compiler.  In WebSphere Application Server 6.0.2 this is
the default compiler used.  However, in WebSphere Application
Server 6.1 and 7.0, this is not the default compiler.
Therefore, in 6.1 and 7.0 this option is only applicable when
used with the useJDKCompiler option.

The fix for this APAR is currently targeted for inclusion in
fixpacks 6.0.2.33, 6.1.0.23, and 7.0.0.3.  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 number
PK72039
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-12
Closed date
2008-11-17
Last modified date
2009-01-16

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK72039: JSPBATCHCOMPILER SKIPS COMPILING JSPS IN DIRECTORY AFTER COMPILE ERROR

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?