"SetPropertiesRule" warning message when starting Tomcat from Eclipse

181,722

Solution 1

From Eclipse Newsgroup:

The warning about the source property is new with Tomcat 6.0.16 and may be ignored. WTP adds a "source" attribute to identify which project in the workspace is associated with the context. The fact that the Context object in Tomcat has no corresponding source property doesn't cause any problems.

I realize that this doesn't answer how to get rid of the warning, but I hope it helps.

Solution 2

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.

Solution 3

Delete the server instance from Eclipse and create a new one.

Share:
181,722

Related videos on Youtube

Michel Elijzen
Author by

Michel Elijzen

Updated on July 08, 2022

Comments

  • Michel Elijzen
    Michel Elijzen almost 2 years

    When I start Tomcat (6.0.18) from Eclipse (3.4), I receive this message (first in the log):

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

    Seems this message does not have any severe impact, however, does anyone know how to get rid of it?

    • Z3ro.Gravity
      Z3ro.Gravity over 12 years
    • BalusC
      BalusC about 8 years
      The currently accepted answer of Alberto Yano is WRONG. Do not blindly herd-upvote it. See also the comments there. The correct answer is in the abovelinked duplicate.
  • Manius
    Manius over 13 years
    Don't you love it when you hear "it's okay to ignore that warning!" If the warning is worthless, why do they show it?? As if we don't have enough real warnings or errors to worry about, we have to have our time wasted on rubbish like this. +1 more reason to ditch Tomcat and upgrade to Glassfish.

Related