tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21419] - error on startup - java.lang.NoSuchMethodException: org.apache.catalina.core.StandardHost.getHost()
Date Wed, 09 Jul 2003 13:15:16 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21419>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21419

error on startup - java.lang.NoSuchMethodException: org.apache.catalina.core.StandardHost.getHost()





------- Additional Comments From hoju@visi.com  2003-07-09 13:15 -------
I'm glad someone else is seeing this.  I tried reproducing it by just running
"$CATALINA_HOME/bin/catalina.bat run", but I didn't see the error occur there.

Here is how you can reproduce it for yourself:

1.  Grab the latest XMLC CVS.  See instructions here:
http://forge.objectweb.org/cvs/?group_id=49

2.  cd to the root of the build and follow short instructions in the "README". 
XMLC should now be built.

3.  cd to $XMLC_ROOT/examples/tomcat.  Copy "build.properties.examples" to
"build.properties" and modify the path to "tomcat.home".  Now run "ant".  This
will build the examples and set up an environment for a custom CATALINA_BASE and
use the value you defined for tomcat.home for CATALINA_HOME.  Convenience
scripts "run-tomcat.bat" and "run-tomcat.sh" will be generated for you.

4.  run the appropriate script for your platform.  I run "run-tomcat.bat" on my
win2k platform.  You should now witness the stack trace that I reported if you
are using the latest Tomcat5 CVS.  To test with another version of tomcat,
modify the tomcat.home property in build.properties to, say..., tomcat-5.0.3 and
re-run "ant".  The scripts will be re-generated for you pointing to the
appropriate CATALINA_HOME.  You should not witness the stack trace using
tomcat-5.0.3.

5.  If you care to view the application running under this custom CATALINA_BASE,
point your browser to:
http://localhost:8081/xmlc/

Hopefully those instructions are clear enough.  Let me know if you have
difficulties.


BTW, regarding your comments...

>Can't you really fix that kind of thing ?
>log4j:WARN No appenders could be found for logger
>(org.apache.catalina.startup.Embedded).
>log4j:WARN Please initialize the log4j system properly.

That started happening in recent Tomcat5 builds.  It doesn't occur when using
Tomcat-4.1.xx and actually didn't occur in early builds of Tomcat5 (sorry, not
sure when exactly it started).  I suspect the reason it is happening has more to
do with commons-logging than Log4j.  I put log4j-1.2.8.jar in
CATALINA_HOME/common/lib as a standard practice.  Since commons-logging sees
Log4j in its classpath, it uses it.  The app in question actually uses no
logging whatsoever so this message is coming from something in Tomcat itself (or
its 3rd party libraries) and not the example application.  If you are asking me
to  track down the issue in commons-logging, you are barking up the wrong tree.
 I have nothing to do with commons-logging and, personally, I feel it has caused
way more pain and suffering than it is worth.  The class loading tricks it uses
to proxy other logging api's fails in lots of situations and is incredibly hard
to debug.  If it were up to me, I'd drop commons-logging like a bad habit and
just use Log4j directly.  I know that won't happen, though, so I'm not going to
press the issue.  I can make Log4j work just fine for me in apps using Log4j
directly so the Log4j warning message in question is pretty innocuous to me. 
I'm not sure if the interaction is adversly affecting Tomcat5 logging when
commons-logging finds Log4j in its classpath or not?  As such, I'm not very
worried about it.  If you want to report a bug I'm all for it, but the only
people who will be able to fix it are either Tomcat guys like yourself or
commons-logging guys.  I don't think many people at Log4j will have much
interest or be able to help in any way other than maybe Yoav Shapira who has
more hands-on experience with commons-logging as well as being a Log4j developer.

Jake

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message