Hi all.

I've been trying to compile the jsp pages using the JSPBatchCompiler batch
file but I keep getting errors like below:


JSPG0045I: Compiling...
D:/WEBSPH~1/APPSER~1/temp/elders-portal/WebSphere_Portal/wps/wps.war/themes/
html/Admin/_PageBarInclude.java:77: cannot resolve symbol
symbol : variable bidiAlignLeft
location: class org.apache.jsp._PageBarInclude
out.print(bidiAlignLeft);
^
D:/WEBSPH~1/APPSER~1/temp/elders-portal/WebSphere_Portal/wps/wps.war/themes/
html/Admin/_PageBarInclude.java:111: cannot resolve symbol
symbol : variable wpsBaseURL
location: class org.apache.jsp._PageBarInclude
out.print( wpsBaseURL );
^
D:/WEBSPH~1/APPSER~1/temp/elders-portal/WebSphere_Portal/wps/wps.war/themes/
html/Admin/_PageBarInclude.java:128: cannot resolve symbol
symbol : variable bidiImageRTL
location: class org.apache.jsp._PageBarInclude
out.print("tab_prev"+bidiImageRTL+".gif");


I've checked the WebSphere portal site and applied the "fix" to
setupCmdLine.bat as shown below:


SET WAS_EXT_DIRS=%JAVA_HOME%/lib;%WAS_HOME%/classes; ...
C:\WebSphere\PortalServer\shared\app;


but still I get this error.

Is there anyone who has WP 5.1 who is also experiencing this problem? More
importantly, have you resolved it?

I have sent the MustGather information to IBM for resolution but they have
been very quiet. I guess I would like to see if I'm the only one or not.

I gather it's just a classpath issue but where?

Anyway, thanks in advance for any help you may offer.

All the best,
Tony

[ Post a follow-up to this message ]

This looks like the JSP batch compiler tries to compile every JSP
separately. However, there are JSPs in portal which include other JSPs.
For example, Default.jsp includes PageBarInclude.jsp. This means you
cannot compile PageBarInclude.jsp separately.

[ Post a follow-up to this message ]

Hi Oliver.

Looks like you hit the nail on the head. All the files that fail are
actually included in other files and I gather they must be incomplete
because of that (and that is the reason they fail compilation).

The file that includes these files though seems to compile OK.

The question that stems from this is, why is it that accessing pages the
first time (after a portal restart) takes so long? It's almost like it is
recompiling the files.

I looked at the list of fixes and came across this:

"PQ97613-After a portal restart, portal access control response time is
higher."

I'll apply this and let you know how it goes.

All the best,
Tony


"Oliver Meyer" <meyer_oliver@gmx.de> wrote in message
news:d0peec$3jum$1@news.boulder.ibm.com...
> This looks like the JSP batch compiler tries to compile every JSP
> separately. However, there are JSPs in portal which include other JSPs.
> For example, Default.jsp includes PageBarInclude.jsp. This means you
> cannot compile PageBarInclude.jsp separately.

[ Post a follow-up to this message ]

Hi all.

Well that worked... and worked well. The speed increase was incredible.
(That plus disabling all the logging we were doing)

Anyway, thanks all.

All the best,
Tony


"Tony Cooke" <TCooke@elders.com.au> wrote in message
news:d0r4tf$58si$1@news.boulder.ibm.com...
> Hi Oliver.
>
> Looks like you hit the nail on the head. All the files that fail are
> actually included in other files and I gather they must be incomplete
> because of that (and that is the reason they fail compilation).
>
> The file that includes these files though seems to compile OK.
>
> The question that stems from this is, why is it that accessing pages the
> first time (after a portal restart) takes so long? It's almost like it is
> recompiling the files.
>
> I looked at the list of fixes and came across this:
>
>     "PQ97613-After a portal restart, portal access control response time
is
> higher."
>
> I'll apply this and let you know how it goes.
>
> All the best,
> Tony
>
>
> "Oliver Meyer" <meyer_oliver@gmx.de> wrote in message
> news:d0peec$3jum$1@news.boulder.ibm.com... 
>
>

[ Post a follow-up to this message ]