I have a set up where tomcat is supposed to start on boot via an rc
shell script on a Linux system (tomcat 4.1.18). I have this
intermittent failure mode where tomcat fails to start up on reboot.
I can _always_ trigger this failure by deleting all tomcat log files,
and then rebooting. After
This even happens if I type the IP address, rather than a hostname. I'd
really like it to not do this, and just use the hostname or IP address
that I type in, but I can't seem to find any hook to change this
behavior. Can anybody help?
Noel Rappin
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,
.
Thanks,
Noel
Shapira, Yoav wrote:
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
We seem to have been able to get the error stack traces by adding the
init-param fork to the JSP servlet, with a value of false. Any idea
why this works?
Noel
Noel Rappin wrote:
There is a root cause, but it doesn't have the error info...
java.lang.ClassNotFoundException
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 working -- doesn't seem to have any impact.
We're
: class org.apache.jsp.foo_jsp
[javac] more cowbell
[javac] ^
[javac] 2 errors
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130)
...
-Tim
Noel Rappin wrote:
Okay. I did a clean install of tomcat. I placed a compilation error
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
/webapp /... eating the exception and not
logging? (Which would be odd, since I would think this would always be
logged)
-Tim
Noel Rappin wrote:
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
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 a compilation failure, but not the compiler message
compiler error is saved or logged. Is there any way to find the
actual text of the compiler error so that we can track it down?
Noel Rappin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
that I need to change?
Thanks,
Noel Rappin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
://a.teslab.hostname.com is being incorrectly rewritten to
http://a.hostname.com. Is there a setting that will prevent the
hostname on the request from changing?
Thanks,
Noel Rappin
-
To unsubscribe, e-mail: [EMAIL PROTECTED
instead of the JRE (we actually distribute the web
application, so it's not a question of just having one copy on our
server)? How do other people manage this in practice?
Thanks,
Noel Rappin
-
To unsubscribe, e-mail: [EMAIL
15 matches
Mail list logo