One other thought: I notice that the compiler messages look like ant
messages -- could the problem be that ant is not in my classpath or
system path some related ant setting?
Noel
Noel Rappin wrote:
I replicated this experiment exactly in my environment. Tomcat
4.1.24, Linux, JSDK 1.4.1_01.
Interesting... can you point me to more information, or has this been
discussed on this list?
Noel
Jason Bainbridge wrote:
I haven't really been following this thread but is this the problem where in
some scenarios that JAVA_HOME/bin needs to be in the system PATH?
Regards,
Subject: Re: JSP Compiler output?
I replicated this experiment exactly in my environment. Tomcat 4.1.24,
Linux, JSDK 1.4.1_01. Is it a Linux thing?
Here's my stack trace in localhost:
org.apache.jasper.JasperException: Unable to compile class for JSP
at
org.apache.jasper.JspCompilationContext.load
It's cropped up a few times on the list, maybe do a search for JAVA_HOME/bin
(or with a backslash instead) at http://tomcatfaq.sf.net
Have you tried doing this yet? It might just work. :)
Regards,
--
Jason Bainbridge
http://jblinux.org
On Wed, 18 Jun 2003 19:09, Noel Rappin wrote:
ChemInformatics
-Original Message-
From: Noel Rappin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 4:59 PM
To: Tomcat Users List
Subject: Re: JSP Compiler output?
I replicated this experiment exactly in my environment. Tomcat 4.1.24,
Linux, JSDK 1.4.1_01. Is it a Linux thing?
Here's my
Starting with a clean install looks like the way to go. Then add one jsp
which contains a compile error and you'll see where the error messages go.
From there - continue to add your components (piecewise if possible) and
find the breaking point.
-Tim
Noel Rappin wrote:
The log4j thing isn't
Okay. I did a clean install of tomcat. I placed a compilation error in
one of the example JSPs. I am now seeing this in the logs:
* catalina.out: start/stop messages
* localhost_examples: a stack trace saying that there was a
JasperException: unable to compile class for JSP
* localhost_log:
You should get something somewhere. For example ... With 4.1.24 (win2k,
jdk1.3, but 1.4 is the same result), I have a file called foo.jsp (at /) with
the contents:
% more cowbell %
My error screen is attached. In the logs (localhost_log.2003-06-17.txt) I get:
2003-06-17 16:34:06
I replicated this experiment exactly in my environment. Tomcat 4.1.24,
Linux, JSDK 1.4.1_01. Is it a Linux thing?
Here's my stack trace in localhost:
org.apache.jasper.JasperException: Unable to compile class for JSP
at
I haven't really been following this thread but is this the problem where in
some scenarios that JAVA_HOME/bin needs to be in the system PATH?
Regards,
--
Jason Bainbridge
http://jblinux.org
On Wed, 18 Jun 2003 04:58, Noel Rappin wrote:
I replicated this experiment exactly in my environment.
Howdy,
This isn't the full stack trace: please post the full one with the Root
Cause.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Noel Rappin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 4:59 PM
To: Tomcat Users List
Subject: Re: JSP Compiler output?
I
Funny how that's his *problem*;)
The bug is deliberate. The problem is: Why isn't there a full stack
trace?
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 4:17 PM
To: Tomcat Users List
Subject: RE: JSP Compiler output?
Howdy
I did. Doesn't seem to be there. Is there a setting I'm missing?
Noel
Tim Funk wrote:
Check localhost_log.xxx
-Tim
Noel Rappin wrote:
We're porting an application from JRun to Tomcat, and we're having
one large issue... When a JSP compile fails on the Tomcat Server,
the log message just
It should be somewhere into the $TOMCAT_HOME/logs/ directory. If its not ...
- If your running windows service - is it in an event log? (guessing)
- Is your server.xml writing to any other logs files?
- Is your JSP/servlet/webapp /... eating the exception and not logging?
(Which would be odd,
The localhost file is there, but the JSP compiler messages are not
winding up there -- we're getting a message in the app file saying that
there was a compilation failure, but not the compiler message saying
where and what the failure is.
We're running on linux, log4j is in the application
In log4j - try turning up logging for jasper, (for example in log4j.properties)
log4j.category.org.apache.jasper=info
-Tim
Noel Rappin wrote:
The localhost file is there, but the JSP compiler messages are not
winding up there -- we're getting a message in the app file saying that
there was
When tools I use eat (or re-translate) messages I want, I tend to try
getting the same behaviour without the tool ...
Have you tried pre-compiling the JSP's?
G'luck
tim
Tim Funk wrote:
In log4j - try turning up logging for jasper, (for example in
log4j.properties)
The log4j thing isn't working -- doesn't seem to have any impact. We're
trying a clean tomcat build to see if we introduced a setting or a
library somewhere that's causing the problem. Should we be expecting to
see these messages at all?
Tim Shaw wrote:
When tools I use eat (or
We're porting an application from JRun to Tomcat, and we're having one
large issue... When a JSP compile fails on the Tomcat Server, the log
message just says that there was a failure, but doesn't say what the
compiler error actually is. We can't seem to find any place where the
actual
Check localhost_log.xxx
-Tim
Noel Rappin wrote:
We're porting an application from JRun to Tomcat, and we're having one
large issue... When a JSP compile fails on the Tomcat Server, the log
message just says that there was a failure, but doesn't say what the
compiler error actually is. We
20 matches
Mail list logo
