JSP Compilation Problem in Tomcat 5.0.28

I am having problem after i deploy my applcation in tomcat 5.0.28. While accessing a jsp an excpetion is generated:
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
Note: Recompile with -Xlint:unchecked for details.
1 error
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
     org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:332)
     org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:412)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:472)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Help on this is appricated.
-Nilesh

Show me the code

Similar Messages

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]

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]

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.

Compile problem using TOMCAT 5.0 and Apache ANT

I got some sample from book.
i just follow the step, place it the class file. it work. it run. show all the detail.
but when i wan to compile it from java file, error came out
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Error allocating a servlet instance
     org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     java.lang.Thread.run(Unknown Source)
root cause
java.lang.NoClassDefFoundError: com/jspbook/HelloWorld (wrong name: HelloWorld)
     java.lang.ClassLoader.defineClass1(Native Method)
     java.lang.ClassLoader.defineClass(Unknown Source)
     java.security.SecureClassLoader.defineClass(Unknown Source)
     org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1634)
     org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:860)
     org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307)
     org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189)
     org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     java.lang.Thread.run(Unknown Source)
note The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs.in CMD:
set java_home = C:\Program Files\Java\jdk1.5.0_08
set classpath = C:\Program Files\Apache Software Foundation\Tomcat 5.0\common\lib
and Apache tomcat originally dont have servlet.jar but servlet-api.jar, i copy the servlet.jar from my friend
i compile it using Apache ANT
here the build.xml
<?xml version="1.0" ?>
<project name="jspbook" default="build" basedir=".">
<target name="build">
    <echo>Starting Build </echo>
    
    <antcall target="tomcatOff"/>
    
    <antcall target="compile"/>
    
    <antcall target="tomcatOn"/>
    <echo>Build Finished </echo>
</target>
<target name="tomcatOff">
    <echo>Turning Off Tomcat </echo>
    <exec executable="bash" os="Windows">
      <arg value="../../bin/shutdown.bat"/>
    </exec>
    <exec executable="bash" os="Linux">
      <arg value="../../bin/shutdown.sh"/>
    </exec>
</target>
<target name="tomcatOn">
    <echo>Starting Tomcat </echo>
    <exec executable="bash" os="Windows">
      <arg value="../../bin/startup.bat"/>
    </exec>
    <exec executable="bash" os="Linux">
      <arg value="../../bin/startup.sh"/>
    </exec>
</target>
<target name="compile">
    <javac
      srcdir="WEB-INF/classes"
      extdirs="WEB-INF/lib:../../common/lib"
      classpath="../../common/lib/servlet.jar"
      deprecation="yes"
      verbose="no">
      <include name="com/jspbook/**"/>
    </javac>
</target>
</project>compile success, but error in IE
paste the sample class file in,restart tomcat. i work again!
what is the problem!
even i compile the code inside the Jcreator, after set required libraries to servlet.jar or servlet-api.jar
compile it, success then run it in IE, same error!!!.
what should i do.
stil a beginer in servlet and jsp anyway.

and Apache tomcat originally dont have servlet.jar but servlet-api.jar, i copy the servlet.jar from my friend servlet.jar is an OLD version, you should only use servlet-api.jar!
wrong name: HelloWorldPerhaps there is a mistake in the class or packagename of the source file. Post the source here.

JSP Compilation Problems With JSTL tags

My JSP worked well when I used JSP expressions, scriptlets, .... I tried to use JSTL instead and encountered some compilation problems. I am unable to see my mistakes and need help:
Problme #1:
int offset = 0;
try
   <c:set var="offset" value="${requestScope.offset}" />
catch ( Exception e )
    // do nothing
}The above code has two compilation errors:
Generated servlet error:
[javac] Compiling 1 source file
illegal start of expression
<c:set var="offset" value="${requestScope.offset}" />
^
Generated servlet error:
';' expected
<c:set var="offset" value="${requestScope.offset}" />
^
Problem #2:
<c:set var="threadBean" value="${requestScope.ThreadBean}" />
int threadID_int = ParamUtil.getParameterInt( request, "thread" );
<c:if test="${threadBean.threadID} != threadID_int">
    throw new AssertionException( "The two threadID are not the same." );
</c:if>Generated servlet error:
illegal start of expression
<c:if test="${threadBean.threadID != threadID_int}">
^

I have deleted the Java code around the JSTL tags. Now, what is wrong with this <c:if test=" ... "> tag? It seems that I have problems to get JSTL tags right.
It seems that I have problems to get JSTL tags right....
<c:if test="${attachBean.attachMimeType.startsWith('image/')}">
     <html:img page="getattachment?attach=<c:out value='${attachBean.attachID}' />" alt="<c:out value='${attachBean.attachFilename}' />" title="<c:out value='${attachBean.attachFilename}' />" border="0" />
</c:if>error message:
74: tag = 'if' / attribute = 'test': An error occurred while parsing custom action attribute "test" with value "${attachBean.attachMimeType.startsWith('image/')}": Encountered "(", expected one of ["}", ".", ">", "gt", "<", "lt", "==", "eq", "<=", "le", ">=", "ge", "!=", "ne", "[", "+", "-", "*", "/", "div", "%", "mod", "and", "&&", "or", "||"]

UTF-8 encoded JSPs compilation problem

Hi,
          I'm using Weblogic 9.0 Beta. I have an XML-format UTF-8 encoded JSP (with the proper encoding declarations). I can see that this is compiled into a UTF-8 Java servlet by WebLogic.
          At the compilation to a class file though, the encoding is corrupted. I guess that the Java compiler is assuming a system-encoded (which would be ISO-8859-1) Java file instead of the actual UTF-8 encoding.
          This problem did not occur with WebLogic 8.1.
          I have tried to explicitly tell the Java compiler to treat the source files as UTF-8 in weblogic.xml, i.e.
          <jsp-param>
          <param-name>compileFlags</param-name>
          <param-value>-encoding UTF8</param-value>
          </jsp-param>
          but that had no effect.
          Anyone else noticed this?
          I assume that correct behaviour is for WebLogic to preserve encoding from JSP to servlet to class file, rather than for me to set encoding in weblogic.xml. Is that correct?
          Is there a workaround?
          Thanks for any help you can offer!

Solved
It is about Tomcat's character encoding not about the codes..
For more info:
[http://wiki.apache.org/tomcat/Tomcat/UTF-8]

Newbie: jsp compile error w/ tomcat 5.0.19

Hello there, this is my first time try to write something in jsp/ servlets, and i encounter a minor installation problem:
using mdk linux with j2sdk1.4.2 (locate at /usr/local/), tomcat is also locate at /usr/local.
I am able to see HelloServlet.java, and HelloWorld.html at http://localhost:8080/servlet/HelloServlet
and http://localhost:8080/testing/HelloWorld.html
but i'm unable to see HelloWorld.jsp at http://localhost:880/HellowWorld.jsp (my HelloWorld.html and HellowWorld.jsp are locate at the same dir)
here's are the things i added in my /etc/profile so far:
CATALINA_HOME="/usr/local/Tomcat"
export CATALINA_HOME
JAVA_HOME="/usr/local/j2sdk1.4.2"
export JAVA_HOME
JavaPath="/usr/local/j2sdk1.4.2/bin"
export JavaPath
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
export PKG_CONFIG_PATH
CLASSPATH=$CLASSPATH:/usr/local/Tomcat/common/lib/servlet-api.jar:/usr/local/Tomcat/
common/lib/jsp-api.jar:/home/allen/programming/j2ee/:./
export CLASSPATH
when do java -verison, i see:
[root@localhost local]# java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
when start tomcat, i got:
[root@localhost bin]# ./startup.sh
Using CATALINA_BASE: /usr/local/Tomcat
Using CATALINA_HOME: /usr/local/Tomcat
Using CATALINA_TMPDIR: /usr/local/Tomcat/temp
Using JAVA_HOME: /usr/local/j2sdk1.4.2
i thought i did everything that was told, yet i can't see jsp page on my browser, while i can see servlets and html,
thank you for your time in advance ^_^

sorry, it was a typo, yea...it was for http://localhost:8080/testing/Hello.jsp
this morning, i copied "tool.jar" from j2sdk1.4.2 to my /usr/local/tomcat/common/lib, restarted, fire it up again using "./catalina.sh" just to see where the problems came from, and here's where the compile error occue:
Compile failed; see the compiler error output for details.
        at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:978)
        at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:799)
        at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:387)
        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:458)
        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
        at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:553)
        at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:291)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:284)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:257)
        at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
        at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:245)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:199)
        at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184)
        at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164)
        at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:156)
        at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972)
        at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:833)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:732)
        at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:619)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:688)
        at java.lang.Thread.run(Thread.java:534)
Mar 16, 2005 7:28:37 AM org.apache.jasper.compiler.Compiler generateClass
SEVERE: Env: Compile: javaFileName=/usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_//org/apache/jsp/testing/Hello_jsp.java
    classpath=/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/classes/:/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/lib/catalina-root.jar:/usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_:/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/classes/:/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/lib/catalina-root.jar:/usr/local/jakarta-tomcat-5.0.19/shared/classes/:/usr/local/jakarta-tomcat-5.0.19/common/classes/:/usr/local/jakarta-tomcat-5.0.19/common/endorsed/xercesImpl.jar:/usr/local/jakarta-tomcat-5.0.19/common/endorsed/xmlParserAPIs.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/ant.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-collections.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-dbcp-1.1.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-el.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-pool-1.1.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/jasper-compiler.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/jasper-runtime.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/jmx.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/jsp-api.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-common.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-factory.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-java.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-resources.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/servlet-api.jar:/usr/local/jakarta-tomcat-5.0.19/common/lib/tools.jar:/usr/local/j2sdk1.4.2/lib/tools.jar:/usr/local/jakarta-tomcat-5.0.19/bin/bootstrap.jar:/usr/local/jakarta-tomcat-5.0.19/bin/commons-logging-api.jar:/usr/local/j2sdk1.4.2/jre/lib/ext/sunjce_provider.jar:/usr/local/j2sdk1.4.2/jre/lib/ext/dnsns.jar:/usr/local/j2sdk1.4.2/jre/lib/ext/ldapsec.jar:/usr/local/j2sdk1.4.2/jre/lib/ext/localedata.jar
    cp=/usr/local/j2sdk1.4.2/lib/tools.jar:/usr/local/Tomcat/bin/bootstrap.jar:/usr/local/Tomcat/bin/commons-logging-api.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/classes
    cp=/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/lib/catalina-root.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_
    cp=/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/classes
    cp=/usr/local/jakarta-tomcat-5.0.19/webapps/ROOT/WEB-INF/lib/catalina-root.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/shared/classes
    cp=/usr/local/jakarta-tomcat-5.0.19/common/classes
    cp=/usr/local/jakarta-tomcat-5.0.19/common/endorsed/xercesImpl.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/endorsed/xmlParserAPIs.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/ant.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-collections.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-dbcp-1.1.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-el.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/commons-pool-1.1.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/jasper-compiler.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/jasper-runtime.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/jmx.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/jsp-api.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-common.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-factory.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-java.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/naming-resources.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/servlet-api.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/common/lib/tools.jar
    cp=/usr/local/j2sdk1.4.2/lib/tools.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/bin/bootstrap.jar
    cp=/usr/local/jakarta-tomcat-5.0.19/bin/commons-logging-api.jar
    cp=/usr/local/j2sdk1.4.2/jre/lib/ext/sunjce_provider.jar
    cp=/usr/local/j2sdk1.4.2/jre/lib/ext/dnsns.jar
    cp=/usr/local/j2sdk1.4.2/jre/lib/ext/ldapsec.jar
    cp=/usr/local/j2sdk1.4.2/jre/lib/ext/localedata.jar
    work dir=/usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_
    extension dir=/usr/local/j2sdk1.4.2/jre/lib/ext
    srcDir=/usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_
    include=org/apache/jsp/testing/Hello_jsp.java
Mar 16, 2005 7:28:37 AM org.apache.jasper.compiler.Compiler generateClass
SEVERE: Error compiling file: /usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_//org/apache/jsp/testing/Hello_jsp.java     [javac] Compiling 1 source file
    [javac] /usr/local/jakarta-tomcat-5.0.19/work/Catalina/localhost/_/org/apache/jsp/testing/Hello_jsp.java:48: cannot resolve symbol
    [javac] symbol : class Data
    [javac] location: package util
    [javac]       out.print( new java.util.Data() );
    [javac]                               ^
    [javac] 1 error
Mar 16, 2005 7:32:34 AM org.apache.jasper.compiler.Compiler generateClass
looking over the compiler error, it seems to me tomcat is able to recongize /usr/local/j2sdk1.4 's location. which i assume it implied JAVA_HOME and CLASSPATH are setup correctly.
Dunno why it just won't display jsp pages and kept saying compiler error...
thank you for helping

JSP compilation problem when upgrading JVM fron JDK1.2.2 to JDK1.3 on Solaris with WLS5.1

Hi
I am trying to upgrade our JVM from JDK1.2.2 to JDK1.3.
When i finally got a clean compile of the code, i get the following error when i try to access the
index.jsp of our site.
ti mai 01 10:33:24 WEST 2001:<I> <WebLogicServer> WebLogic Server started
ti mai 01 10:35:22 WEST 2001:<I> <ServletContext-General> Generated java file:
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java
ti mai 01 10:35:22 WEST 2001:<E> <ServletContext-General> Compilation of
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java failed:
java.io.IOException: Not enough space
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:54)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:551)
at java.lang.Runtime.exec(Runtime.java:477)
at java.lang.Runtime.exec(Runtime.java:443)
at weblogic.utils.Executable.exec(Executable.java:170)
at weblogic.utils.Executable.exec(Executable.java:107)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:423)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
java.io.IOException: Compiler failed executable.exec([Ljava.lang.String;[/usr/bin/javac, -classpath,
/usr/java1.3/jre/lib/rt.jar:/usr/java1.3/jre/lib/i18n.jar:/usr/java1.3/jre/lib/sunrsasign.jar:/usr/j
ava1.3/jre/classes:/usr/local/weblogic/510/9/weblogic510sp9boot.jar:/usr/local/weblogic/510/weblogic
/classes/boot::/usr/local/weblogic/510/9/telenormobilHTTP302.jar:/usr/local/weblogic/510/9/weblogic5
10sp9.jar:./djuicecluster/wamp/lib/client.jar:/usr/local/weblogic/510/weblogic/license:/usr/local/we
blogic/510/weblogic/classes:/usr/local/weblogic/510/weblogic/myserver/serverclasses:/usr/local/weblo
gic/510/weblogic/lib/weblogicaux.jar:./djuicecluster/serverclasses:./djuicecluster/serverclasses/lda
pjdk.jar:./djuicecluster/serverclasses/nslookup.jar:./djuicecluster/serverclasses/activation.jar:./d
juicecluster/serverclasses/bsfengines.jar:./djuicecluster/serverclasses/bsf.jar:./djuicecluster/serv
erclasses/mail.jar:./djuicecluster/serverclasses/xalan.jar:./djuicecluster/serverclasses/xerces.jar:
./djuicecluster/serverclasses/jsse.jar:./djuicecluster/serverclasses/Acme.jar:./djuicecluster/server
classes/xml.jar:./djuicecluster/serverclasses/poppers.jar:./djuicecluster/serverclasses/com_telenor.
jar:./djuicecluster/serverclasses/smpp.jar:./djuicecluster/serverclasses/smpputils.jar:./djuiceclust
er/serverclasses/entrust.jar:./djuicecluster/projects/djuice/lib/djuice_common.jar:./djuicecluster/s
erverclasses/oreilly.jar:./djuicecluster/projects/djuice/lib:./djuicecluster/projects/djuice/lib/Men
uBean.jar:./djuicecluster/projects/djuice/lib/CategoryContentBean.jar:./djuicecluster/projects/djuic
e/servletsnclasses:/usr/local/weblogic/510/weblogic/lib/jConnect.jar:/usr/local/weblogic/510/weblogi
c/lib/jconn2.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15392.jar:/db
dump/weblogic/510/weblogic/lib/persistence/WebLogic_RDBMS.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15393.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15394.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15395.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15396.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15397.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15398.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15399.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15400.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15401.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15402.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15403.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15404.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15405.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15406.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15407.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15408.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15409.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15410.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15411.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15412.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15413.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15414.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15415.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15416.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15417.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15418.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15419.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15420.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15421.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15422.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15423.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15424.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15425.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15426.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15427.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15428.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15429.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15430.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15431.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15432.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15433.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15434.jar:./djuicecluster/projects/djuice/servletsnclasses:./djuicecluster/projects/djui
ce/servletclasses:/dbdump/djuice/djuice.17b/djuicecluster/classfiles, -d,
/dbdump/djuice/djuice.17b/djuicecluster/classfiles,
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java])
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:439)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
ti mai 01 10:35:22 WEST 2001:<E> <ServletContext-General> Servlet failed with Exception
java.io.IOException: Compiler failed executable.exec([Ljava.lang.String;[/usr/bin/javac, -classpath,
/usr/java1.3/jre/lib/rt.jar:/usr/java1.3/jre/lib/i18n.jar:/usr/java1.3/jre/lib/sunrsasign.jar:/usr/j
ava1.3/jre/classes:/usr/local/weblogic/510/9/weblogic510sp9boot.jar:/usr/local/weblogic/510/weblogic
/classes/boot::/usr/local/weblogic/510/9/telenormobilHTTP302.jar:/usr/local/weblogic/510/9/weblogic5
10sp9.jar:./djuicecluster/wamp/lib/client.jar:/usr/local/weblogic/510/weblogic/license:/usr/local/we
blogic/510/weblogic/classes:/usr/local/weblogic/510/weblogic/myserver/serverclasses:/usr/local/weblo
gic/510/weblogic/lib/weblogicaux.jar:./djuicecluster/serverclasses:./djuicecluster/serverclasses/lda
pjdk.jar:./djuicecluster/serverclasses/nslookup.jar:./djuicecluster/serverclasses/activation.jar:./d
juicecluster/serverclasses/bsfengines.jar:./djuicecluster/serverclasses/bsf.jar:./djuicecluster/serv
erclasses/mail.jar:./djuicecluster/serverclasses/xalan.jar:./djuicecluster/serverclasses/xerces.jar:
./djuicecluster/serverclasses/jsse.jar:./djuicecluster/serverclasses/Acme.jar:./djuicecluster/server
classes/xml.jar:./djuicecluster/serverclasses/poppers.jar:./djuicecluster/serverclasses/com_telenor.
jar:./djuicecluster/serverclasses/smpp.jar:./djuicecluster/serverclasses/smpputils.jar:./djuiceclust
er/serverclasses/entrust.jar:./djuicecluster/projects/djuice/lib/djuice_common.jar:./djuicecluster/s
erverclasses/oreilly.jar:./djuicecluster/projects/djuice/lib:./djuicecluster/projects/djuice/lib/Men
uBean.jar:./djuicecluster/projects/djuice/lib/CategoryContentBean.jar:./djuicecluster/projects/djuic
e/servletsnclasses:/usr/local/weblogic/510/weblogic/lib/jConnect.jar:/usr/local/weblogic/510/weblogi
c/lib/jconn2.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15392.jar:/db
dump/weblogic/510/weblogic/lib/persistence/WebLogic_RDBMS.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15393.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15394.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15395.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15396.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15397.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15398.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15399.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15400.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15401.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15402.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15403.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15404.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15405.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15406.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15407.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15408.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15409.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15410.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15411.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15412.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15413.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15414.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15415.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15416.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15417.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15418.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15419.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15420.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15421.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15422.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15423.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15424.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15425.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15426.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15427.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15428.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15429.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15430.ja
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15431.jar:/dbdump/djuice/dju
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15432.jar:/dbdump/djuice/djuice.17b/djuicecluste
r/dj_app6/tmp_deployments/ejbjar15433.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
ments/ejbjar15434.jar:./djuicecluster/projects/djuice/servletsnclasses:./djuicecluster/projects/djui
ce/servletclasses:/dbdump/djuice/djuice.17b/djuicecluster/classfiles, -d,
/dbdump/djuice/djuice.17b/djuicecluster/classfiles,
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java])
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:439)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
None of my filesystems are full. Why does this error occur then.
I have tried to check the jsp configuration but there is nothing to see there ...
Can annyone help me with this problem ?
Thanks
Ståle Tomten

Hi
I solved the problem.
The server did not have enough memory available to spawn the javac process... Therefor: Not enough
space.
I just reduced the memory set up for weblogic and it worked.
regards
Ståle Tomten
"Ståle Tomten" <[email protected]> wrote in message news:[email protected]...
Hi
I am trying to upgrade our JVM from JDK1.2.2 to JDK1.3.
When i finally got a clean compile of the code, i get the following error when i try to access the
index.jsp of our site.
ti mai 01 10:33:24 WEST 2001:<I> <WebLogicServer> WebLogic Server started
ti mai 01 10:35:22 WEST 2001:<I> <ServletContext-General> Generated java file:
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java
ti mai 01 10:35:22 WEST 2001:<E> <ServletContext-General> Compilation of
/dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java failed:
java.io.IOException: Not enough space
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:54)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:551)
at java.lang.Runtime.exec(Runtime.java:477)
at java.lang.Runtime.exec(Runtime.java:443)
at weblogic.utils.Executable.exec(Executable.java:170)
at weblogic.utils.Executable.exec(Executable.java:107)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:423)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
java.io.IOException: Compiler failedexecutable.exec([Ljava.lang.String;[/usr/bin/javac, -classpath,
>
/usr/java1.3/jre/lib/rt.jar:/usr/java1.3/jre/lib/i18n.jar:/usr/java1.3/jre/lib/sunrsasign.jar:/usr/j
>
ava1.3/jre/classes:/usr/local/weblogic/510/9/weblogic510sp9boot.jar:/usr/local/weblogic/510/weblogic
>
/classes/boot::/usr/local/weblogic/510/9/telenormobilHTTP302.jar:/usr/local/weblogic/510/9/weblogic5
>
10sp9.jar:./djuicecluster/wamp/lib/client.jar:/usr/local/weblogic/510/weblogic/license:/usr/local/we
>
blogic/510/weblogic/classes:/usr/local/weblogic/510/weblogic/myserver/serverclasses:/usr/local/weblo
>
gic/510/weblogic/lib/weblogicaux.jar:./djuicecluster/serverclasses:./djuicecluster/serverclasses/lda
>
pjdk.jar:./djuicecluster/serverclasses/nslookup.jar:./djuicecluster/serverclasses/activation.jar:./d
>
juicecluster/serverclasses/bsfengines.jar:./djuicecluster/serverclasses/bsf.jar:./djuicecluster/serv
>
erclasses/mail.jar:./djuicecluster/serverclasses/xalan.jar:./djuicecluster/serverclasses/xerces.jar:
>
./djuicecluster/serverclasses/jsse.jar:./djuicecluster/serverclasses/Acme.jar:./djuicecluster/server
>
classes/xml.jar:./djuicecluster/serverclasses/poppers.jar:./djuicecluster/serverclasses/com_telenor.
>
jar:./djuicecluster/serverclasses/smpp.jar:./djuicecluster/serverclasses/smpputils.jar:./djuiceclust
>
er/serverclasses/entrust.jar:./djuicecluster/projects/djuice/lib/djuice_common.jar:./djuicecluster/s
erverclasses/oreilly.jar:./djuicecluster/projects/djuice/lib:./djuicecluster/projects/djuice/lib/Men>uBean.jar:./djuicecluster/projects/djuice/lib/CategoryContentBean.jar:./djuicecluster/projects/djuic>e/servletsnclasses:/usr/local/weblogic/510/weblogic/lib/jConnect.jar:/usr/local/weblogic/510/weblogi>c/lib/jconn2.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15392.jar:/db>dump/weblogic/510/weblogic/lib/persistence/WebLogic_RDBMS.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15393.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15394.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15395.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15396.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15397.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15398.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15399.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15400.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15401.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15402.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15403.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15404.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15405.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15406.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15407.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15408.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15409.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15410.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15411.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15412.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15413.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15414.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15415.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15416.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15417.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15418.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15419.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15420.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15421.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15422.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15423.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15424.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15425.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15426.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15427.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15428.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15429.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15430.ja>r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15431.jar:/dbdump/djuice/dju>ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15432.jar:/dbdump/djuice/djuice.17b/djuicecluste>r/dj_app6/tmp_deployments/ejbjar15433.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy>ments/ejbjar15434.jar:./djuicecluster/projects/djuice/servletsnclasses:./djuicecluster/projects/djui> ce/servletclasses:/dbdump/djuice/djuice.17b/djuicecluster/classfiles, -d,> /dbdump/djuice/djuice.17b/djuicecluster/classfiles,> /dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java)at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:439)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
ti mai 01 10:35:22 WEST 2001:<E> <ServletContext-General> Servlet failed with Exception
java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[/usr/bin/javac, -classpath,
>
/usr/java1.3/jre/lib/rt.jar:/usr/java1.3/jre/lib/i18n.jar:/usr/java1.3/jre/lib/sunrsasign.jar:/usr/j
>
ava1.3/jre/classes:/usr/local/weblogic/510/9/weblogic510sp9boot.jar:/usr/local/weblogic/510/weblogic
>
/classes/boot::/usr/local/weblogic/510/9/telenormobilHTTP302.jar:/usr/local/weblogic/510/9/weblogic5
>
10sp9.jar:./djuicecluster/wamp/lib/client.jar:/usr/local/weblogic/510/weblogic/license:/usr/local/we
>
blogic/510/weblogic/classes:/usr/local/weblogic/510/weblogic/myserver/serverclasses:/usr/local/weblo
>
gic/510/weblogic/lib/weblogicaux.jar:./djuicecluster/serverclasses:./djuicecluster/serverclasses/lda
>
pjdk.jar:./djuicecluster/serverclasses/nslookup.jar:./djuicecluster/serverclasses/activation.jar:./d
>
juicecluster/serverclasses/bsfengines.jar:./djuicecluster/serverclasses/bsf.jar:./djuicecluster/serv
>
erclasses/mail.jar:./djuicecluster/serverclasses/xalan.jar:./djuicecluster/serverclasses/xerces.jar:
>
./djuicecluster/serverclasses/jsse.jar:./djuicecluster/serverclasses/Acme.jar:./djuicecluster/server
>
classes/xml.jar:./djuicecluster/serverclasses/poppers.jar:./djuicecluster/serverclasses/com_telenor.
>
jar:./djuicecluster/serverclasses/smpp.jar:./djuicecluster/serverclasses/smpputils.jar:./djuiceclust
>
er/serverclasses/entrust.jar:./djuicecluster/projects/djuice/lib/djuice_common.jar:./djuicecluster/s
>
erverclasses/oreilly.jar:./djuicecluster/projects/djuice/lib:./djuicecluster/projects/djuice/lib/Men
>
uBean.jar:./djuicecluster/projects/djuice/lib/CategoryContentBean.jar:./djuicecluster/projects/djuic
>
e/servletsnclasses:/usr/local/weblogic/510/weblogic/lib/jConnect.jar:/usr/local/weblogic/510/weblogi
>
c/lib/jconn2.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15392.jar:/db
>
dump/weblogic/510/weblogic/lib/persistence/WebLogic_RDBMS.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15393.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15394.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15395.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15396.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15397.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15398.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15399.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15400.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15401.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15402.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15403.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15404.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15405.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15406.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15407.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15408.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15409.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15410.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15411.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15412.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15413.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15414.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15415.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15416.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15417.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15418.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15419.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15420.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15421.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15422.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15423.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15424.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15425.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15426.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15427.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15428.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15429.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15430.ja
>
r:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15431.jar:/dbdump/djuice/dju
>
ice.17b/djuicecluster/dj_app6/tmp_deployments/ejbjar15432.jar:/dbdump/djuice/djuice.17b/djuicecluste
>
r/dj_app6/tmp_deployments/ejbjar15433.jar:/dbdump/djuice/djuice.17b/djuicecluster/dj_app6/tmp_deploy
>
ments/ejbjar15434.jar:./djuicecluster/projects/djuice/servletsnclasses:./djuicecluster/projects/djui
ce/servletclasses:/dbdump/djuice/djuice.17b/djuicecluster/classfiles, -d,> /dbdump/djuice/djuice.17b/djuicecluster/classfiles,> /dbdump/djuice/djuice.17b/djuicecluster/classfiles/jsp_servlet/_index.java)at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:439)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:245)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:369)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
None of my filesystems are full. Why does this error occur then.
I have tried to check the jsp configuration but there is nothing to see there ...
Can annyone help me with this problem ?
Thanks
Ståle Tomten

Jsp compilation problem in IAS ?.

None of the JSP's present in a directory with a name "default" gets compiled . I get the javac exception given below.
Tried it out with Fortune sample application by creating a drectory with a name "default" .Even a simple jsp with a "hello" string also fails . Is "default" some kind of key word in IAS .
javac error: /usr/local/iplanet/ias6.new/ias/APPS/fortune/fortune/WEB-INF/compiled_jsp/jsp/APPS/fortune/default/test.java:1: Identifier expected. package jsp.APPS.fortune.default; Superclass HttpJspBase of class test not found. public class test extends HttpJspBase { ^ 2 errors

Hi,
I can give you a quick answer that this could be an issue. However, I would like to experiment and prove by testing across various platform and different service packs. Please let me know more details, especially on the default directory, like where the directory resides, how you have packaged the application and what is the name of the application etc. This will help me to replicate the problem and conclude at a solution.
Thanks & Regards
Ganesh .R
Developer Technical Support
Sun Microsystems
http://www.sun.com/developers/support

JSP compile problem - Scriptlet

Hello,
I'm using weblogic 10.3.
I have problem when i run a web application.
The problem is accured when weblogic try to compile jsp page that contains such syntax :
*<jsp:param name="messageKey" value="<%=request.getParameter("noCebMessageKey")%>" />*
When i change this assertion to :
*<%String msg = request.getParameter("noCebMessageKey");%>*
*<jsp:param name="messageKey" value="<%=msg%>" />*
It works fine..
This problem is general with all syntax like this : value="<%=<java instruction>%>
It's a big problem, becaus the application contains more than 2000 jsp pages..
Are there any special config to add to weblogic configuration files to resolve this problem ?
Thanks

Hi WhietacapeTech ,
Normally you cannot do the following which u are trying currently because of the Double Quote Mark Opening and Closing...will awlsya create the issue...:
<jsp:param name="messageKey" value="<%=request.getParameter("noCebMessageKey")%>" />
Alternate option: (Use JSTL [*Java Standard Tag Library]*)
Example:
*<%@ taglib uri="/WEB-INF/tld/c.tld" prefix="c" %>*
*<jsp:param name="messageKey" value="<c:out value='${param.noCebMessageKey}' " />*
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are here)

JSP compile problem

I'm using the expanded WAR file approach. I have a JSP that specifies
          a usebean like so:
          <jsp:useBean id="Dummy"
          class="com.myapp.Dummy"
          scope="session">
          </jsp:useBean>
          Dummy.class is part of a jar file that resides in the WEB-INF/lib dir of
          the web app. The JSP invokes methods against Dummy and it all works as expected.
          The problem is that I have added another method to Dummy and no matter what
          I do, I cannot get the servlet engine to compile it. The compile always fails on the
          line in the JSP where it is invoking the newly added method to Dummy, for example:
          Dummy.doNewMethod() // <----compiler points here saying it can't resolve symbol 'doNewMethod'.
          Here's what I have tried:
          - recompiling and rejaring Dummy.class and putting it back in the WAR dir
          - shutting down the appserver (and servlet engine )
          - deleting the generated files in tmpwar where the .java and .class files are gened by servelet
          engine
          - cleared the cache on the browser
          - shut browser down
          - rebooted
          - took Dummy.class out of the jar and made sure that the bits had the new method
          Nothing seems to work. I know the code works because I have a java app written against the same
          Dummy.class and that works just fine.
          Any help would be most appreciated..
          Thanks.


hi
did u include the package path and the clientjar file in the J2EE_CLASSPATH env variable in the j2ee_insallfolder\bin\userconfig.bat file.if not try it and restart the server .
hope this works for u :-)

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>

Jboss ide jboss eclipse jsp compile problem

Hi i downlaoded eclipse with jboss ide plugin for jsp support.
now configuration is jboos server + eclipse + jboss ide but i am not able to cmpile jsp pages.even though jboss server is running on eclipse no problem in that.
thanxs in advance

Do I have to use JBoss with Tomcat or am I missing
something at configuration?You're missing something. I'll bet the problem's in your JSP file, not JBoss/Jetty - unless you've dorked with the default settings and done something to make it not work. And you don't need the j2ee12.jar in your CLASSPATH - it's already there, otherwise JBoss/Jetty wouldn't run.

JSP Compilation Problem in Tomcat 5.0.28

Similar Messages

Maybe you are looking for