[Mark McCraw]

I have spent the last 3 days trying to get something, *anything*, working with MyEclipse and have had no success. I have read through all of the help documents, and none of the step by step tutorials work. Could it be that I am using a Macintosh? Has anyone ever successfully used MyEclipse on the Mac?

Here is a specific example. I am trying to work my way through the “Working With Web Projects – Quickstart” document. I am able to create a web project, add a JSP file, and edit it. However, the validation features described in the document do not work in my JSP editor. No matter how flagrantly wrong I make the syntax, nothing gets highlighted when I save, or even when I explicitly tell it to “Validate JSP”. It always says the syntax is valid.

The next problem I encounter is when I try to deploy the HelloWorld project. I am using Tomcat 4 for my application server. I am able to successfully deploy the project as an Exploded archive and I am able to verify that the files get moved to the right place on the filesystem. I am even able to verify that the “Sync-on-Demand” feature of the exploded deployment works by changing a file within MyEclipse and then looking at the corresponding file in tomcat’s webapps directory: they stay sync’ed like they should.

The problem comes when I try to start tomcat from eclipse (please note that I never have a problem starting tomcat from a regular shell). When I choose “Start” from the application server management menu, the Console spits out tons of nasty things:

May 25, 2005 1:11:55 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
GlobalResourcesLifecycleListener: Exception processing Global JNDI Resources
javax.naming.NamingException: /usr/local/jakarta-tomcat-4.1.31/conf/tomcat-users.xml.new (Permission denied)
at org.apache.naming.NamingContext.lookup(NamingContext.java:797)
at org.apache.naming.NamingContext.lookup(NamingContext.java:147)
at org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(GlobalResourcesLifecycleListener.java:167)
at org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.createMBeans(GlobalResourcesLifecycleListener.java:134)
at org.apache.catalina.mbeans.GlobalResourcesLifecycleListener.lifecycleEvent(GlobalResourcesLifecycleListener.java:102)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2136)
at org.apache.catalina.startup.Catalina.start(Catalina.java:463)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156)
Starting service Tomcat-Standalone
Apache Tomcat/4.1.31
javax.naming.NamingException: /usr/local/jakarta-tomcat-4.1.31/conf/tomcat-users.xml.new (Permission denied)
at org.apache.naming.NamingContext.lookup(NamingContext.java:797)
at org.apache.naming.NamingContext.lookup(NamingContext.java:147)
at org.apache.catalina.realm.UserDatabaseRealm.start(UserDatabaseRealm.java:250)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1126)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143)
at org.apache.catalina.startup.Catalina.start(Catalina.java:463)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156)
Catalina.start: LifecycleException: No UserDatabase component found under key UserDatabase
LifecycleException: No UserDatabase component found under key UserDatabase
at org.apache.catalina.realm.UserDatabaseRealm.start(UserDatabaseRealm.java:257)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1126)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143)
at org.apache.catalina.startup.Catalina.start(Catalina.java:463)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156)
Stopping service Tomcat-Standalone
Catalina.stop: LifecycleException: Coyote connector has not been started
LifecycleException: Coyote connector has not been started
at org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:1296)
at org.apache.catalina.core.StandardService.stop(StandardService.java:499)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2178)
at org.apache.catalina.startup.Catalina.start(Catalina.java:494)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156)

Most of this seems to have to do with the permissions of /usr/local/jakarta-tomcat-4.1.31/conf/, which I have set to 777 in a fruitless attempt to resolve the problem.

If I start tomcat from a shell, it starts without any error messages (and nothing in the error logs), but if I then try to access the HelloWorld project I have deployed (http://localhost:8080/HelloWorld/helloWorld.jsp) I get the following message: “The requested resource (/HelloWorld/helloWorld.jsp) is not available.” This strikes me as bizarre, because <tomcat-root>/webapps/HelloWorld/helloWorld.jsp definitely exists on the filesystem. Could it be a file permissions problem somewhere? Is there any way to tell what could be going wrong?

I am at a loss at how to proceed. All of the documentation has been practically useless to me. I cannot find any troubleshooting documentation that addresses the problems I’m having. Do I have a configuration problem either with Eclipse, MyEclipse, or Tomcat? How can I tell? What should I do next to try to make this work? I like MyEclipse, but can’t possibly use it if I can’t make something basic like HelloWorld work. Please help.

What operating system and version are you running? Mac OS 10.3.9
What Eclipse version and build id are you using? (Help > About Eclipse Platform) Version: 3.1.0 Build id: I20050513-1415
– Was Eclipse freshly installed for MyEclipse? yes
– If not, was it upgraded to its current version using the update manager?
– Are any other external plugins installed? no
– How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.* 4
What MyEclipse version are you using? (Help > About Eclipse Platform > Features) Version: 3.1.0
Build id: I20050513-1415
What JDK version are you using to run Eclipse? (java -version)
java version “1.4.2_05”
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-141.4)
Java HotSpot(TM) Client VM (build 1.4.2-38, mixed mode)

What JDK version are you using to launch your application server? 1.4.2
What steps did you take that resulted in the issue? see above
What application server are you using? jakarta-tomcat-4.1.31
Are there any exceptions in the Eclipse log file? (<workspace>/.metadata/.log) The log has gotten far too large to post here

[Riyad Kalla]

1) You need to have “javac” in your system path so the JSP validator can find it for validating the JSP pages.

2) DO NOT try and install/run Eclipse/MyEclipse/Tomcat as different users if you are a first time user. please install everything in your home dir and run it from there, your problems so far sound exactly like permission issues that simply put a developer does not have time to fool around with, so just make it easy and stick it in your home dir and run everything from there.

3) The version of MyEclispe you gave above is not correct, please tell me the value from your Window > Preferences > MYEclipse page. From your Eclipse BuildID it looks like you are running Eclipse 3.1M7, so make sure you dwonloaded the correct beta version of MyEclipse to go along with it.

4) Running on a mac is fine except for a few bugs pertaining specificall to the Eclipse platform and the Mac, but we are hopign the Eclipse team fixes them in 3.1.

[Mark McCraw]

Hi Riyad. Thanks so much for the reply. It put me on the right track, I think. Here is what I learned: The big problem of not having any of the deployed stuff work seems to have been Tomcat 4. I began to start reinstalling everything in my home directory like you suggested, and decided that while I was at it I might as well get Tomcat 5 and install it, and lo and behold, the problems all went away! That is, I can now run helloWorld.jsp from the Eclipse deployment. Just for the sake of completeness, I installed it both in my home directory as well as in /usr/local/, and it worked the same either place. So it looks like the file permission problems were just some sort of wild goose chase that Tomcat 4 sent us on.

Regarding the JSP validator, I confirmed that javac was in my system path, but it still doesn’t work. I even went so far as to specify “-vm /usr/bin/java” when I launched Eclipse from the command line, but got the same result. After much googling, I found the following post (from this forum, actually)from last Monday: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-7319-highlight-jsp+validation.html. I am in fact using 3.1M7, so it looks like it may actually be a bug. Do you know if there has been any kind of update on this?

Regarding the version of MyEclipse that I am running, my apologies on the misinformation. The version info I get from Window > Preferences > MYEclipse page is:
Version: 3.8.4+QF2-BetaFor3.1M7
Build Id: 200505151200-3.8.4+QF2-BetaFor3.1M7

Thanks again for your help.

[Riyad Kalla]

It sounds like your last problem (validation) is infact the bug we have in our M7 build, so you are all setup until we get a new bugfix release out!

[Mark McCraw]

This is good to know. JSP validation sounds like a nice feature, but certainly isn’t critical to development. I am glad to know it isn’t something obvious that I am missing. Thanks again for your quick help. I can get back to development now!

[Author]

Posts