- This topic has 10 replies, 2 voices, and was last updated 18 years, 4 months ago by Riyad Kalla.
-
AuthorPosts
-
PatFlaniganMemberI am using Eclipse 3.2 RC 7 and the MyEclipse version 5 Milestone 1. I am running on a Mac – Intel version, hence I need the Eclipse 3.2. When I try to start Tomcat 5 I get the following exception.
java.lang.NoSuchMethodException: org.apache.catalina.startup.Catalina.setAwait(boolean)
at java.lang.Class.getMethod(Class.java:1581)
at org.apache.catalina.startup.Bootstrap.setAwait(Bootstrap.java:358)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:430)I’ve not been able to figure out why. I am running with the latest 1.5 JDK for the mac.
Help
Riyad KallaMemberGo to your Tomcat connector settings and write them all here for me. Also did you change any settings under Launch or Paths or were those left default? (debug and empty)
PatFlaniganMemberThe Tomcat connector settings are:
/usr/local/apache-tomcat-5.5.17 for Home and Base and /usr/local/apache-tomcat-5.5.17/temp for Temp.The Launch and Paths were left default (debug and empty)
Riyad KallaMemberI can’t reproduce this. Try this, download TOmcat here: http://apache.cs.utah.edu/tomcat/tomcat-5/v5.5.17/bin/apache-tomcat-5.5.17.tar.gz
unzip it to your Desktop, launch MyEclipse, change the directory to pont at the new one and try and run it. Did it work?
PatFlaniganMemberDownloaded the apache, and made it part of the desktop. Still fails. Is there something in the configuration that could be picking up the wrong thing?
PatFlaniganMemberHow do you handle the missing tools.jar in the Apple JDK. The files that are usually part of tools.jar are in a Classes/classes.jar or various other jars that are part of the Classes directory. I’ve looked at setclasspath.sh script that is part of Tomcat and it looks like there is a hack that is intended to fix this. However I don’t see that it could possibly work. Maybe they haven’t tested throughly, or I just don’t understand what they are doing with JIKESPATH.
Riyad KallaMemberPat I’m going to do some more testing on my end in a day or two and get back to you, I appologize for the lag in responding. We are prepping Milestone 2 and it has everyone busy to the bone.
PatFlaniganMemberRiyad,
Thanks for the update. From what I can deduce, you probably just use the tomcat startup scripts. If that is true, during the startup setclasspath.sh gets invoked. In this script there is some code near the bottom that attempts to compensate for the missing tool.jar.
# OSX hack to CLASSPATH
JIKESPATH=
if [ `uname -s` = “Darwin” ]; then
OSXHACK=”/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Classes”
if [ -d “$OSXHACK” ]; then
for i in “$OSXHACK”/*.jar; do
JIKESPATH=”$JIKESPATH”:”$i”
done
fi
fi
This is mostly correct as it goes, but has obvious problems if you are using an older JDK. The main problem I see is that the variable JIKESPATH doesn’t ever seem to get used. This is true in all the versions of Tomcat I’ve looked at, back to 4.1.31. The problem is that even when I change this script to use JIKESPATH, it still doesn’t work right. For some reason this must not be important.In looking at the failure more closely, I see that it does not find the setAwait method in the Catalina class. This can’t be classpath issues as it is running the Bootstrap class in the same jar file. The Catalina class here extends Embedded, and the setAwait method is defined in the super class. I’m puzzled why this is not working, and it probably has nothing to do with MyEclipse, just Tomcat and Mac.
Riyad KallaMemberI can’t reproduce this. All I did was install Eclipse 3.2 GA, MyEclipse 5.0 Milestone 2 (will be out in a few hours) and downloaded Tomcat 5.5.17 and unziped it, then set it up in the MyEclipse connectors and launched it:
I would point out that our connectors do not use the scripts to launch the app servers, the call directly into the Catalina classes. You set the JDK you want to launch your app server with in the “JDK” node under the Tomcat 5 connector settings.
PatFlaniganMemberThanks for your help. Your input made me decide the problem was software migration
problem from a powermac to the mac mini. This resulted in some kind of configuration
problem I never go a handle on. So I rebuilt the OS from scratch erasing everything there.
Now things work without a hitch.
Riyad KallaMemberSorry to hear you had to do the big-bomb approach, but I’m glad to hear everything is working now.
-
AuthorPosts