Continuing problems about JSP compilation...

          I have two problems that I can't solve about JSP:
          - my JSPs aren't recompiled when I modify them
          I've got to redeploy the entire webApp for the
          modification to be updated.
          - the precompilation of my JSPs fails
          I've got the common NullPointerException in JSP2Java.makeReader
          I'm working in the deployed directory way, with a WL6.0sp2...
          My xml files seem to be correct and the clocks of the different machines are synchronized.
          I read several threads and solutions concerning those problems but all of these
          were applied and it still doesn't work...
          If someone could help me... TIA...

          JimmyL wrote:
          > I have two problems that I can't solve about JSP:
          >
          > - my JSPs aren't recompiled when I modify them
          > I've got to redeploy the entire webApp for the
          > modification to be updated.
          On admin server or managed server????
          >
          >
          > - the precompilation of my JSPs fails
          > I've got the common NullPointerException in JSP2Java.makeReader
          >
          Answered in the other email..
          Kumar
          >
          > I'm working in the deployed directory way, with a WL6.0sp2...
          > My xml files seem to be correct and the clocks of the different machines are synchronized.
          >
          > I read several threads and solutions concerning those problems but all of these
          > were applied and it still doesn't work...
          >
          > If someone could help me... TIA...

Similar Messages

Urgent Solution needed--Problem in JSP compilation with JDK 1.5 and JDK 1.6

Hi,
I m using JDK 1.5 and Tomcat 5.0 the problem is that after starting server when I m going to access my application at that time instead of displaying HomePage it directly display the blank page on screen.
After analyzing tomcat log I have found that there was a problem with JSP page compilation.
The exception logged in Tomcat Log is given below
An error occurred at line: 1 in the generated java file
The type Collection is not generic; it cannot be parameterized with arguments <? extends E>
Stacktrace:
*     at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92)*
*     at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)*
*     at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:423)*
*     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:308)*
*     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)*
*     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)*
*     at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)*
*     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317)*
*     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)*
*     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)*
*     at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)*
*     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)*
*     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)*
*     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654)*
*     at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:447)*
*     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)*
*     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292)*
*     at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:424)*
*     at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:343)*
*     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)*
*     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)*
*     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)*
*     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)*
*     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)*
*     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)*
*     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)*
*     at java.lang.Thread.run(Thread.java:619)*
After getting this kind of error I have analyzed my code furhter then I came to know that there was problem with static include tag.
In my jsp page I have used following line which is the main cause of error
<%@ include file="top.jsp" %>If I ommit this line then it is working properly.
Instead of static include I have used jsp:include also.
Still I m getting same problem.
We have to migrated from JDK 1.5 to 1.6 and Tomcat 5.0.28 to 6.0.14, still same problem is there.
We have tried a lot but didnt get success to overcome this problem.
If anybody having any solution then ur each reply will be appreciated.
Thanks in advance..........!!!!!!!
Edited by: JBOSS2000 on Jan 15, 2008 9:29 AM

Hi "mshanu" and "amit" Thanks for ur replies Here I m posting the code of "top.jsp"........!!!!
<%@ page errorPage="errordisplay.jsp"%>
<table cellpadding="0"
       cellspacing="0" height=50 width=780>
       <tbody>
         <tr class="header">
           <td class="logo"><IMG SRC="assets/Logo.gif" BORDER=0 ALIGN=top></td>
           <td align="right"><span class="applicationtitle"><%@ include file="/contents/logo.htm" %></span><br>
           <span class="companyname"><%@ include file="/contents/companyname.htm" %></span></td>
         </tr>
        </tbody>
</table>To include top.jsp I have tried
<jsp:include page="top.jsp" flush="true">
</jsp:include>
         AND
<%@ include file="top.jsp"%>but none of this worked.
If I remove the include then It is working properly.
But I need inluded file too so that I am wondoring for the solution.
This problem seems very wiered to me. I dont know why it is happening.
This problem is started only when I used the TOMCAT 6.14.
Is it the bug of TOMCAT 6.14 or What somebody Plz help.
I got stuck here.........!!!!!!!!!!
It doesn't seem any problem with top.jsp. As per my thinking the problem is there in include due to that it doesn't compile the JSP page in Tomcat 6.0.
Earlier I am having same code running on the Tomcat 5.0.28 and JDK 1.5.0.
But problem occured when I have used Tomcat 6.x...!!

Problem about c++ compiler in intel computer

we used forte c++ compiler (version 6) under solaris on intel computer
but I can't find the misalign or align debug option flags about the CC
and when the program exit,there are errors reported:no map at the fault address
stoped at the delete statement releasing the memory
but not all delete statement report error
the same code works well on sparc station
I want to know if it is the problem of byte align
and how can I set the CC complier to align or misalign(can't find it in the CC -help)

The default location for the Sun C++ compiler is
/opt/SUNWspro/bin/CC
You can download it from
http://www.sun.com/forte/cplusplus/buy.html
The GNU C++ is free - download it from
http://sunfreeware.com/
(Or in your Solaris 8 companion CD)
No, there is no standard C++ compiler in the core Solaris packages.

A problem about jsp:include

When I use
<jsp:include page="list.jsp" >
<jsp:param name="year" value="2002" />
</jsp:include>
how can I get the value of the param year in the jsp list.jsp?

yes, but from JSTL.
but to use it, you have to
in your jsp
<%@ taglib uri="jstl-core" prefix="c"%>
in your web.xml
<taglib>
<taglib-uri>jstl-core</taglib-uri>
<taglib-location>/WEB-INF/c.tld</taglib-location>
</taglib>
in your /WEB-INF folder put c.tld (and the other JSTL tld files if you want)
and jstl.jar in your /WEB-INF/lib folder.
The JSTL tag lib provide a lot of possibility ...
Regards.

JSP compilation with javac runs out of memory in WL 6.1

Hello
          I have a problem with JSP compilation in WL 6.1. It throws OutOfMemory exceptions very often. I have set memory settings (-Xms128m -Xmx356m) and WL console shows that there is a lot of free memory, still is does not help.
          Can I use jikes instead of javac ? Latest jikes generates code which is not compatible for JDK 1.3, so it does not work for WL 6.1 either.
          Any suggestions ?
          Maris

Hi.
I have checked Java Doc for repeat tag on
http://e-docs.bea.com/wls/docs61/javadocs/weblogicx/jsp/tags/RepeatTag.html.
java.lang.Object
|
+-javax.servlet.jsp.tagext.TagSupport
|
+-javax.servlet.jsp.tagext.BodyTagSupport
|
+-weblogicx.jsp.tags.RepeatTag
According to the API, it should be a tag pair with tag body. I also tried
your code, I has the exactly the same Error message in browser. I understood
it is an example from http://e-docs.bea.com/wls/docs61///////pdf/jsp.pdf.
I strongly suggest you to post this message to news group
weblogic.developer.interest.jsp instead.
Thanks.
BEA Weblogic Support
"Hans Nemarich" <[email protected]> wrote in message
news:3bcc8384$[email protected]..
>
Hi, I have the following problem when i try to use the weblogic-tags.jarincluded
with wl6.1. I have copied the file and is referenced by the classpath. I`mtrying
to run the example included in the docs:
Parsing of JSP File '/HelloWeblogic.jsp' failed:
/HelloWeblogic.jsp(15): no corresponding open tag for tag extensionclose: //[
null; Line: 15]
probably occurred due to an error in /HelloWeblogic.jsp line 15:
</wl:repeat>
### this is the jsp file: ###
<html>
<head>
<%@ taglib uri="weblogic-tags.tld" prefix="wl" %>
<title>Hello Weblogic</title>
</head>
<body bgcolor="#FDF5E6">
<h2>
Weblogic Custom Tags
</h2>
<hr>
<wl:repeat id="name" set="<%= new String[] { "sam", "fred", "ed" } %>">
<%= name %>
</wl:repeat>
</body>
</html>
### ...and this the web.xml file: ####
<taglib>
<taglib-uri>weblogic-tags.tld</taglib-uri>
<taglib-location>
/WEB-INF/lib/weblogic-tags.jar
</taglib-location>
</taglib>
Someone can help me ?

Re: [iPlanet-JATO] sp3 jsp compiler problem

Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text
substitution situations, and as a completely independent tool its use is not
restricted to migration situations (or file types for that matter).
Second, I sympathize with the unfortunate trouble you are experiencing due to
Jasper's (perhaps more strict) compilation, but in what way did the iMT
automated translation contribute to these inconsistencies that you cited?
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a
translation situation, the only way "OnClick" would have been introduced was if
it had been part of the pre-existing project's "extraHTML" (which was written
by the original customer and just passed through unchanged by the iMT) or if it
was added manually by the post-migration developer.
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
similar to the OnClick situation described above?
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no
equivalent in the NetDynamics world, so any content tags in your code must have
been introduced by your developers manually. Its a shame that jasper is so
particular, but the iMT could not help you out here even if we wanted to. The
constants that are used by the iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
[Non-text portions of this message have been removed]

Thanks a lot Matt and Mike for your prompt replies.
I agree completely that iMT doesn't introduce the inconsistencies.
About the three cases I mentioned, the third one happens only in
manually created JSPs. So it has nothing to do with iMT. The first
two are mainly due to the existing HTML code, as you rightly pointed
out.
The reason I made the suggestion is since we know that case 1 and 2
won't pass the japser compiler in sp3, we have to do something about
it. The best place to do this, in my mind, is iMT. Of course, there
might be some twists that make it impossible or difficult to do this
kind of case manipulation or attribute discard.
Weiguo
--- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
tool its use is not restricted to migration situations (or file types
for that matter).
>
Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
in what way did the iMT automated translation contribute to these
inconsistencies that you cited?
>
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
introduced was if it had been part of the pre-existing
project's "extraHTML" (which was written by the original customer and
just passed through unchanged by the iMT) or if it was added manually
by the post-migration developer.
>
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
>
>
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
in your code must have been introduced by your developers manually.
Its a shame that jasper is so particular, but the iMT could not help
you out here even if we wanted to. The constants that are used by the
iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
see, the only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
>
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as
what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
>>
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
Service.
>
>
>
[Non-text portions of this message have been removed]

JSP compile problems

Hello,
I have my jsp pages deployed in a war in an ear. The manifest in the war lists my dependent jars. In my orion-web.xml, I have the include-war-manifest-class-path parameter set to "true". This seems to work at runtime in that the jsp pages can locate the dependent jars. However my problem is at compile time. The compiler doesn't seem to find the jars and the compile fails. If I move the jars to web-inf/lib the compile will work, however that kind of defeats the purpose of having them in the Manifest.mf file.
Anyone have any suggestions?
Thanks,
Mike Sander

<p>Sebastian,</p>
<p>Its unclean to include your java files in a jar. I can't remember reading anything about not including java files in the jar file spec though. In your jar file are the java files in the correct package structure?</p>
<p>
Hussein Badakhchani</br>
</p>

HELP.....!!!!! Chinese jsp compilation problem.....

Hi,
Could someone please help on the above mentioned?
I'm using JDeveloper 3.2.3 for my program development under Chinese windows platform. I have created a simple JSP page, which contains few static Chinese words and I have included the line
<%@ page contentType="text/html;charset=UTF-8"%>
at the top of the page. When I tried to compile it using encoding "UTF8" (under compiler option), the compiler gave me this error:
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.jsp
Error: (0) sun.io.MalformedInputException.
Btw, when I have removed the line <%@ page contentType="text/html;charset=UTF-8"%> from the page and compile, I've got this error:
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.jsp
Warning: (0) ISO-8859-1 character set may not match project compiler setting.
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.java
Error: (0) malformed input character in C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.java.
I do appreciate your help on this. Thank you.

Here's some info one of the JSP Developers sent me:
1. HELP.....!!!!! Chinese jsp compilation problem.....
The customer is trying to parse a document generated by
Windows's notepad. When saved in UTF-8, the byte
order mark is saved too. We have a know bug that
JSP parser doesn't recognize Byte Order Mark. The
bug is : 1915285.
2. CHINESE CHARACTER ON JSP
. SQLPLUS depends on NLS_LANG setting. If you
check the windows registry, the default of NLS_LANG
depends on the OS. The user environment is Traditional
Chinese, so does NLS_LANG. If we set NLS_LANG
to .UTF8, SQLPLUS dumps the data in UTF8, however,
the command prompt will have problem displaying them.
. For JSP, as mentioned in a previous mail:
<%@ page contentType="text/html;charset=UTF-8" %> for all languages
<%@ page contentType="text/html;charset=GB2312" %> for simplified Chinese
<%@ page contentType="text/html;charset=Big5" %> for traditional Chinese
. When you enter Chinese characters on a browser,
the data is automatically converted to page encoding
(UTF-8 in your case) before sent back to the server.
But your receiving servlet/JSP needs to have request
encoding set correctly.
    I'm not sure about the JDeveloper environment,
but here is a simple JSP you may try to verify your
OC4J environment:
a.    To set up the schema:
connect scott/tiger
create table tab01(col varchar2(100));
b. Edit the connect string in nls.jsp
c. Run the nls.jsp in oc4j instance.

<%@ page contentType="text/html; charset=UTF-8" %>
<%@ page import="oracle.jdbc.*,java.sql.*,java.io.*"%>
<HTML>
<HEAD>
<TITLE>Hello</TITLE></HEAD>
<BODY>
<%
request.setCharacterEncoding("UTF-8");
String sampledata="\u7D20";
String paramValue = request.getParameter("myparam");
String connStr = "jdbc:oracle:thin:@dlsun478:5521:j2ee01";
String user = "scott";
String passwd = "tiger";
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection(connStr, user, passwd);
if (paramValue == null || paramValue.length() == 0) { %>
   <FORM METHOD="GET">
   Please input your name: <INPUT TYPE="TEXT" NAME="myparam"
value="<%=sampledata%>" size=20>
<BR>
   <INPUT TYPE="SUBMIT" value="Insert Data">
   </FORM>
<%
selectData(conn, out);
else
%>
   <H1> Insert Data: <%= paramValue %> </H1>
   <br/>
<%
insertData(conn, paramValue);
%>
<a href="nls.jsp">back</a>
<%
%>
</BODY>
</HTML>
<%!
public void insertData(Connection aConn, String myval)
    try {
      PreparedStatement stmt = aConn.prepareStatement("insert into tab01
values(?)");
      stmt.setString(1, myval);
      stmt.executeUpdate();
      aConn.close();
    catch (SQLException e) {
      e.printStackTrace();
public void selectData (Connection aConn, JspWriter out)
    try {
      Statement stmt = aConn.createStatement( );
      ResultSet r = stmt.executeQuery("SELECT col FROM tab01");
      out.println("<H1>List of Data:</H1>");
      while (r.next()) {
        out.println(r.getString(1)+"<br/>");
      aConn.close();
    catch (SQLException e) {
      e.printStackTrace();
    catch (IOException e) {
      e.printStackTrace();
%>

Facing Jsp Compilation Problem in the Server

Hai all,
I get the following problem when i try to call a jsp in my browser.
javax.servlet.ServletException: org.eclipse.jdt.internal.compiler.env.NameEnvironmentAnswer.<init>(Lorg/eclipse/jdt/internal/compiler/env/IBinaryType;Lorg/eclipse/jdt/internal/compiler/env/AccessRestriction;)V
This problem exists only with my new war of the application and the tomcat works fine with older version .war of the same application.
I thought i could be some mis-match in the library files version in the tomcat and the one in the lid of application.
Please give me suggestions as early as possible

Thanks For Your Replys,
I found the Solution in the following manner.
Problem was the as mentioned with the version of jar files in the lib of tomcat and the lib of Application war file. I had my war files of higher versions than in tomcat. Hence i upgraded the tomcat version not the lib version of tomcat. Because there was this problem of tomcat compilation of the jsp code is not supported.
Thanks Guys.

Jdeveloper jsp compile problem:too large

I am getting following error when i try to run the jsp page(I am using embedded oc4j10.1.3.3)
Error: code segment of method _jspService(javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse) too large
The jsp is over 2000 lines long.
Any help would be appreciate.
Thanks
Kalee

Hi,
you can try and change the compiler to Javac
Also you might want to think about jsp:includes that include JSP snippets from external files at compile time. A JSP with 2000 lines seems to be quite large and may better be broken up into pieces
Frank

URGENT: sp6 and JSP compiling/classpath problem?

Hi,
          We installed sp6 on our production site a little over a week and started
          seeing this problem on our logs with regards to any JSP with an include tag,
          such as:
          <%@ include file="/inc/insideHeadTag.jsp" %>
          INTERMITTENTLY, we will get the following error in the page on the client
          side at runtime:
          < ! -- cannot include file '/inc/insideHeadTag.jsp', resource not
          found -- >
          I grepped this newsgroup and noticed a previous unanswered post of the same
          nature, "Static compiles do not seem to include JSP's". Except in our case,
          this problem also manifest for dynamic JSP compiles, happens sporatically,
          and only started with sp6.
          Bug???
          Gene Chuang
          Join Kiko.com!


          Just to clarify - I'm not from BEA, I'm from EA - short a letter.
          As far as I know, there is no synchronization between WL instances in a cluster regarding the
          the compiling of JSPs. So when you start up two WL instances that share the same workingDir,
          and each WL instances gets a hit on your shiny new index.jsp, they both need to compile it. So the first
          one compiles it and writes index.class, the second does the same, overwriting the first _index.class,
          possibly at the same time that the first instance is trying to load _index.class into memory. And you
          get a mysterious 'class not found' error. Not likely, but possible.
          "Gene Chuang" <[email protected]> wrote:
          >Hmm, interesting... I thought Weblogic strongly recommends clustered
          >servers sharing the same file system?
          >
          >So you're saying the system-wide, cluster and node specific directories can
          >reside on the shared drive, but workingDirs should reside on local drives?
          >
          >--
          >Gene Chuang
          >Join Kiko.com!
          >
          >"Mike Reiche" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Make sure that your WLS instances are NOT sharing the workingDir. If two
          >instances
          >> try to compile the same JSP at the same time, bad things can happen.
          >>
          >> Mike
          >>
          >> "Gene Chuang" <[email protected]> wrote:
          >> >Hi Jong,
          >> >
          >> >Thanks for the reply; but I wish the solution is as simple as that.
          >Yes,
          >> >my .jsps are in the proper directory. They have been working properly
          >for
          >> >the past 6 months, since we were running WL 4.5.1. Only when I switched
          >to
          >> >WL 5.1 sp6 did this bug start showing up. Plus, like I said in my
          >original
          >> >post, this bug is sporatic. SOMETIMES the included jsp is found by
          >Weblogic
          >> >and the includer jsp compiles correctly; other times it isn't found and
          >the
          >> >includer jsp leaves a gap! What's going on?
          >> >
          >> >We are running clustered web servers in Solaris 2.7 with a shared file
          >> >system. This sporatic behavior may be because some nodes aren't working
          >> >properly???
          >> >
          >> >--
          >> >Gene Chuang
          >> >Join Kiko.com!
          >> >
          >> >"Jong Lee" <[email protected]> wrote in message
          >> >news:[email protected]...
          >> >>
          >> >> "Gene Chuang" <[email protected]> wrote:
          >> >> >Hi,
          >> >> >
          >> >> >We installed sp6 on our production site a little over a week and
          >started
          >> >> >seeing this problem on our logs with regards to any JSP with an
          >include
          >> >tag,
          >> >> >such as:
          >> >> I assumed insideHeadTag.jsp is in
          >> >> YOUR_DOCUMENT_ROOT/inc/insideHeadTag.jsp
          >> >>
          >> >> if you haven't read the spec of relative URI please do so:
          >> >> jsp spec 1.1 - section 2.5.2
          >> >>
          >> >> Jong
          >> >>
          >> >> >
          >> >> > <%@ include file="/inc/insideHeadTag.jsp" %>
          >> >> >
          >> >> >INTERMITTENTLY, we will get the following error in the page on the
          >client
          >> >> >side at runtime:
          >> >> >
          >> >> > < ! -- cannot include file '/inc/insideHeadTag.jsp', resource not
          >> >> >found -- >
          >> >> >
          >> >> >I grepped this newsgroup and noticed a previous unanswered post of the
          >> >same
          >> >> >nature, "Static compiles do not seem to include JSP's". Except in our
          >> >case,
          >> >> >this problem also manifest for dynamic JSP compiles, happens
          >> >sporatically,
          >> >> >and only started with sp6.
          >> >> >
          >> >> >Bug???
          >> >> >
          >> >> >Gene Chuang
          >> >> >Join Kiko.com!
          >> >> >
          >> >> >
          >> >> >
          >> >>
          >> >
          >> >
          >>
          >
          >

JSP Compile problem with WLS 5.1 sp9

Hi All,
          The attached, simple JSP file uses a custom tag, and some JavaScript. When
          this is compiled into Java, the Java that is created is Bad. It seems as if
          WLS is having problems properly escaping single-quotes and double-quotes.
          Also attached, is the generated Java file. Note around line 82, and compare
          that to around line 15 of the JSP.
          Does anyone have an idea what can be done to fix this? This JSP compiles
          fine under Tomcat 3.2.
          Thanx!
          Will Hartung
          ([email protected])
          [test.jsp]
          [_test.java]


Hi All,
          The attached, simple JSP file uses a custom tag, and some JavaScript. When
          this is compiled into Java, the Java that is created is Bad. It seems as if
          WLS is having problems properly escaping single-quotes and double-quotes.
          Also attached, is the generated Java file. Note around line 82, and compare
          that to around line 15 of the JSP.
          Does anyone have an idea what can be done to fix this? This JSP compiles
          fine under Tomcat 3.2.
          Thanx!
          Will Hartung
          ([email protected])
          [test.jsp]
          [_test.java]

JSP compiler problems/Weird NullPointerException in JSP

[weblogic 4.5.1 sp 10 on NT 4.0 sp4 w/Netscape 4.72, jdk 1.2.2]
          I recently began trying to compile all of my jsp files externally rather
          than depending on the dependency detection. Because I have multiple
          levels of nested files included, I have had a lot of problems making the
          compile work. For example, I have a subdirectory called include. Jsp
          files in the include directory are included from the directory above
          using '<%@ include file="include/filename.jsp" %>'. This works for one
          level of nesting, but there are problems when a file in the include
          subdirectory includes another file in the include subdirectory. Prior
          to installing service packs, specifying 'include/secondfile.jsp' for the
          file parameter worked. After service packs, this code had to be changed
          to just plain 'secondfile.jsp'. Imagine my surprise when I started
          compiling externally and only 'include/secondfile.jsp' would work. If I
          ever touch a jsp file after compiling them all, then the compile invoked
          by the JspServlet will NOT include secondfile unless I also modify the
          include line before the compile happens. This is a MAJOR PAIN, and I
          would like an explanation. How come invoking weblogic.jspc does
          something different than invoking JspServlet through file timestamp
          checking? Also, any ideas for a workaround?
          This leads to my second really annoying problem. After compiling all
          JSPs and restarting weblogic, I get a NullPointerException accessing a
          static method in a particular class. Many pages display correctly until
          this point in the processing, none of which access the problem class. A
          log message before the static method call is printed. A try/catch block
          surrounds the call. The first line in the static message prints another
          log message. This static method log message is not reached, and the
          try/catch block catches a NullPointerException. It seems the class
          reference is null, a situation I have not previously encountered in
          java. The generated java file looks fine, with no other code between
          the log message and the static call. Now here is the rub - if I touch
          the jsp file containing the class reference, with no code change,
          weblogic recompiles it using JspServlet, and then everything works as
          expected. It seems the external compilation is the only factor that
          varies in the failure. I am quite frustrated trying to track this
          'impossible to occur' exception. Any suggestions, advice, or
          workarounds?
          I have searched newsgroups and seen some similar behaviors reported, but
          with no solutions. One person mentioned that the external compile
          should take place with the current directory set to the root. This
          fails completely to find the relative include files.
          Bryan Helm


The includes only work if you invoke the compilation when you are on top of
          the hierrcahy,
          ex foo/bar.jsp
          do a jspc foo/bar.jsp,
          not cd foo
          jscp bar.jsp
          Bryan Helm <[email protected]> wrote in message
          news:[email protected]...
          > [weblogic 4.5.1 sp 10 on NT 4.0 sp4 w/Netscape 4.72, jdk 1.2.2]
          >
          > I recently began trying to compile all of my jsp files externally rather
          > than depending on the dependency detection. Because I have multiple
          > levels of nested files included, I have had a lot of problems making the
          > compile work. For example, I have a subdirectory called include. Jsp
          > files in the include directory are included from the directory above
          > using '<%@ include file="include/filename.jsp" %>'. This works for one
          > level of nesting, but there are problems when a file in the include
          > subdirectory includes another file in the include subdirectory. Prior
          > to installing service packs, specifying 'include/secondfile.jsp' for the
          > file parameter worked. After service packs, this code had to be changed
          > to just plain 'secondfile.jsp'. Imagine my surprise when I started
          > compiling externally and only 'include/secondfile.jsp' would work. If I
          > ever touch a jsp file after compiling them all, then the compile invoked
          > by the JspServlet will NOT include secondfile unless I also modify the
          > include line before the compile happens. This is a MAJOR PAIN, and I
          > would like an explanation. How come invoking weblogic.jspc does
          > something different than invoking JspServlet through file timestamp
          > checking? Also, any ideas for a workaround?
          >
          > This leads to my second really annoying problem. After compiling all
          > JSPs and restarting weblogic, I get a NullPointerException accessing a
          > static method in a particular class. Many pages display correctly until
          > this point in the processing, none of which access the problem class. A
          > log message before the static method call is printed. A try/catch block
          > surrounds the call. The first line in the static message prints another
          > log message. This static method log message is not reached, and the
          > try/catch block catches a NullPointerException. It seems the class
          > reference is null, a situation I have not previously encountered in
          > java. The generated java file looks fine, with no other code between
          > the log message and the static call. Now here is the rub - if I touch
          > the jsp file containing the class reference, with no code change,
          > weblogic recompiles it using JspServlet, and then everything works as
          > expected. It seems the external compilation is the only factor that
          > varies in the failure. I am quite frustrated trying to track this
          > 'impossible to occur' exception. Any suggestions, advice, or
          > workarounds?
          >
          > I have searched newsgroups and seen some similar behaviors reported, but
          > with no solutions. One person mentioned that the external compile
          > should take place with the current directory set to the root. This
          > fails completely to find the relative include files.
          >
          > Bryan Helm
          >

Sleeping thread that was started by startup class: wakes up on jsp compiler run

Hello,
I've ecountered the following unexpected behaviour:
A class defined as a WL startup class creates a thread in the startup() method. This
thread then calls the Thread.sleep method.
So far so good.
Now each time an updated JSP is accessed by a browser, this JSP gets recompiled by
the JSP compiler (so far so good, nothing to do with the startup thread), and each
time this happens, the above mentioned thread wakes up as if his time were up. (Output
is "TestStartupThread: Woken up: timer timed out", see code below)
Anybody know anything??
Code of startup class ( = thread class) listed below.
Dirk
import java.util.Hashtable;
import weblogic.common.*;
public class TestStartupThread extends Thread implements T3StartupDef, T3ShutdownDef
private static TestStartupThread testThread = null;
/** controls running of thread, will be set to false when server shuts down
private static volatile boolean runThread = true;
public void setServices(T3ServicesDef t3def) { }
public String startup(String s, Hashtable ht) {
testThread = new TestStartupThread();
testThread.start();
return "ok";
public String shutdown(String s, Hashtable ht) {
runThread = false;
testThread.interrupt();
return "ok";
public void run() {
while (runThread) {
try {
System.err.println("TestStartupThread: now going to sleep");
Thread.sleep(1000*60*60);
System.err.println("TestStartupThread: Woken up: timer timed out");
} catch (InterruptedException ie) {
System.err.println("TestStartupThread: Woken up by InterruptedException");

Looks like a good use for WL time services.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"Brian Dowd" <[email protected]> wrote in message
news:[email protected]...
>
I am getting exactly the same problem, but I did something
similar (to this & mine) in WL 4.5.1 and it worked OK.
About the best solution we can come up with is to test the time
before and after wake up, if the time is less then go back
to sleep for the new amount of time ...
Does anyone know how to properly do this in WL 5.1 ?
I notice this thread is a bit old ....
"Dirk Rehberger" <[email protected]> wrote:
Hello,
I've ecountered the following unexpected behaviour:
A class defined as a WL startup class creates a thread in the startup()
method. This
thread then calls the Thread.sleep method.
So far so good.
Now each time an updated JSP is accessed by a browser, this JSP gets
recompiled by
the JSP compiler (so far so good, nothing to do with the startup thread),
and each
time this happens, the above mentioned thread wakes up as if his time
were up. (Output
is "TestStartupThread: Woken up: timer timed out", see code below)
Anybody know anything??
Code of startup class ( = thread class) listed below.
Dirk
import java.util.Hashtable;
import weblogic.common.*;
public class TestStartupThread extends Thread implements T3StartupDef,
T3ShutdownDef
private static TestStartupThread testThread = null;
/** controls running of thread, will be set to false when server shuts
down
private static volatile boolean runThread = true;
public void setServices(T3ServicesDef t3def) { }
public String startup(String s, Hashtable ht) {
testThread = new TestStartupThread();
testThread.start();
return "ok";
public String shutdown(String s, Hashtable ht) {
runThread = false;
testThread.interrupt();
return "ok";
public void run() {
while (runThread) {
try {
System.err.println("TestStartupThread: now going to sleep");
Thread.sleep(1000*60*60);
System.err.println("TestStartupThread: Woken up: timer timed
out");
} catch (InterruptedException ie) {
System.err.println("TestStartupThread: Woken up by
InterruptedException");

Problem in jsp with container(JEUS)

Hi I am a developer in Korea
Nowadays I have a problem in jsp pages which have contained some pakage directive in a library path
so my problem is changing some of the classes in the package during service time.
Error result is
-Root Exception stack trace :
-jeus.servlet.jsp.compiler.JspCompileException: fail to compile : source = C:\TmaxSoft\JEUS6.0\webhome\epims_container1\_generated_\j2ee-modules\harweb\jeus_jspwork\_custermg\_html\_mypage\_600_MyReqJob_5fjsp.java, -error msg = C:\TmaxSoft\JEUS6.0\webhome\epims_container1\_generated_\j2ee-modules\harweb\jeus_jspwork\_custermg\_html\_mypage\_600_MyReqJob_5fjsp.java:76: cannot access custermg.MyPageQuery
bad class file: C:\epims\harweb\WEB-INF\classes\custermg\MyPageQuery.class
-class file has wrong version 8241.8224, should be 49.0
-Please remove or make sure it appears in the correct subdirectory of the classpath.
- MyPageQuery myquery = null;
I don't know why this could be happed in random period of time It happens nearly each 10 hours . after this failure, the same error happen in other classes.
Before ten hours?.... No problem with the jsp pages
The number 8241.8224 tells me that it is not generated by java compiler but I don't have any clue but the above error
my run time environment is
- HP Server, Windows Server 2003, 64bit
- Jeus, jdk1.5.0_15
so any help from you will be appreciated...
thanks

Mr. Ahmed,
Excuse-me by my bad english.
I experienced the same problem when surrounded my scripts with comment caracters:

If this is your case, simply uncomment it and the script will work fine.

Continuing problems about JSP compilation...

Similar Messages

Maybe you are looking for