“SetPropertiesRule” warning message when starting Tomcat from Eclipse [duplicate]

Answer 1

I'm finding that Tomcat can't seem to find classes defined in other projects, maybe even in the main project. It's failing on the filter definition which is the first definition in web.xml. If I add the project and its dependencies to the server's launch configuration then I just move on to a new error, all of which seems to point to it not setting up the project properly.

Our setup is quite complex. We have multiple components as projects in Eclipse with separate output projects. We have a separate webapp directory which contains the static HTML and images, as well as our WEB-INF.

Eclipse is "Europa Winter release". Tomcat is 6.0.18. I tried version 2.4 and 2.5 of the "Dynamic Web Module" facet.

Thanks for any help!

• Richard

Answer 2

The solution to this problem is very simple. Double click on your tomcat server. It will open the server configuration. Under server options check ‘Publish module contents to separate XML files’ checkbox. Restart your server. This time your page will come without any issues.

Answer 3

I am using Eclipse. I have resolved this problem by the following:

1. Open servers tab.
2. Double click on the server you are using.
3. On the server configuration page go to server options page.
4. Check Serve module without publishing.
5. Then save the page and configurations.
6. Restart the server by rebuild all the applications.

You will not get any this kind of error.

Answer 4

I am posting my answer because I suspect there might be someone out there for whom the above solutions might not have worked.

So, you are getting a warning,

WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server: (project name)' did not find a matching property.

Rather than disabling this warning by checking that option in Server configuration (I did try that) I would suggest you do this:

1. First close all the existing projects by right clicking in Project explorer.
2. Remove all the projects already synchronized with the server.
3. Remove the server and redeploy it.
4. Create a new dynamic project, do nothing yet just try running this on the server.
5. Check the console, do you get the warning now. (My case I didn't get any).
   This means that something is wrong with your project not with eclipse or the server.
6. Now restart the server. Don't run any app yet.
   You probably know that the Tomcat container loads up context of all the synchronized apps at the start.
7. It will load context of any already synchronized app.
8. Here is the catch, if there is really something wrong in your project it will show the stack trace of the exceptions.Look carefully and you will find where is the bug in your app.

Now if you successfully found that there is a bug in your app, the probable place would be look for a web.xml file which the container uses for loading the app. In my case I had misspelled a name in servlet mapping which made me debug meaninglessly for 3 hours. Your problem might be someplace else.

And another thing, if you have many apps synchronized with the server,there is a possibility some other app's context might be the source of problem. Try debugging one by one.

Answer 5

Servers tab

--> doubleclick servername

--> Server Options: tick "Publish module contexts to separate XML files"

restart your server

Answer 6

I copied the dynamic Webproject before the issue came up. So, changing the org.eclipse.wst.common.component file in the .settings directory solved the issue for me. The other solutions did not work.