Quantcast

warning: Setting property 'source' [...] did not find a matching property.

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

warning: Setting property 'source' [...] did not find a matching property.

Dwight, August
Hey all.

I'm running a Tomcat 6.0.29 server inside Eclipse 3.5.2, on Win7.  I have no build errors or runtime errors.  When I add my web project and start my tomcat server, I see the following warning:

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

When this warning is present, my server starts successfully with no errors, but the application does not appear to start and is not accessible.  If I check the "Publish module contents to separate XML files" box on the server configuration options screen, the warning disappears but my application still does not load, so this might be a red herring.

I found a story from someone with similar symptoms here:

http://blog.rememberoneanother.com/2008/06/12/tomcat-warning-did-not-find-a-matching-property/

Unfortunately, their solution did not work for me either.  (I checked, and I do not have an extraneous WEB-ROOT directory.)

My three teammates are using a similar setup (slightly different minor versions of Eclipse and Tomcat) with no problems.  I also had everything working with my setup at one point, but I accidentally clobbered my workspace earlier this week and I had to start from a fresh one.  I remember having this problem once before, but I just can't seem to remember or recreate whatever I did to fix it.

Has anyone seen or solved a similar problem before?  Any other suggestions?

-August

________________________________
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: warning: Setting property 'source' [...] did not find a matching property.

Christopher Schultz-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

August,

On 9/30/2010 11:05 AM, Dwight, August wrote:
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context}
> Setting property 'source' to 'org.eclipse.jst.j2ee.server:myappname'
> did not find a matching property.

You're trying to set the "source" attribute on your <Context> element.

A few suggestions:

1. Don't set the "source" attribute on your <Connector> (there is no
   such configuration property)
2. Don't put your <Context> in your server.xml. Instead, put it into
   your webapp's META-INF/context.xml file. Don't have one? Create one.

> When this warning is present, my server starts successfully with no
> errors

Not a surprise: that's a warning.

> but the application does not appear to start and is not
> accessible.

That's strange.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyksFgACgkQ9CaO5/Lv0PA+MQCcDil83eLMErpIx9prOqohfVoK
ZBEAnjWfPh/wRkPM1pVdzjz67cDWnI3D
=QKuV
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: warning: Setting property 'source' [...] did not find a matching property.

Caldarale, Charles R
> From: Christopher Schultz [mailto:[hidden email]]
> Subject: Re: warning: Setting property 'source' [...] did not find a matching property.

> You're trying to set the "source" attribute on your
> <Context> element.

Eclipse has the nasty habit of stuffing this illegal attribute there automatically.  Another reason not to run Tomcat under Eclipse.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: warning: Setting property 'source' [...] did not find a matching property.

Caldarale, Charles R
In reply to this post by Dwight, August
> From: Dwight, August [mailto:[hidden email]]
> Subject: warning: Setting property 'source' [...] did not find a matching property.

> I have no build errors or runtime errors.

Are you looking at *all* of the Tomcat logs when you make that statement?  Note that Eclipse obfuscates things to the point where you might not be looking at the real logs for that execution of Tomcat.

What does Tomcat's manager app say about the state of your webapp?

What happens when you run Tomcat by itself, not under Eclipse?

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: warning: Setting property 'source' [...] did not find a matching property.

Dwight, August
> From: Caldarale, Charles R [mailto:[hidden email]]
> Sent: Thursday, September 30, 2010 1:42 PM
> Subject: RE: warning: Setting property 'source' [...] did not find a matching property.

>> I have no build errors or runtime errors.
>
> Are you looking at *all* of the Tomcat logs when you make that statement?

catalina.*.log and localhost.*.log are both clean.

> What does Tomcat's manager app say about the state of your webapp?
>
> What happens when you run Tomcat by itself, not under Eclipse?

When I run Tomcat by itself, my app works the way it should, and Manager says it's running.

> From: Caldarale, Charles R [mailto:[hidden email]]
> Sent: Thursday, September 30, 2010 12:07 PM>
>
> > From: Christopher Schultz [mailto:[hidden email]]
> > Subject: Re: warning: Setting property 'source' [...] did not find a matching property.
>
> > You're trying to set the "source" attribute on your
> > <Context> element.
>
> Eclipse has the nasty habit of stuffing this illegal attribute there automatically.  Another reason not to > run Tomcat under Eclipse.

If there's a convenient way to do all of the things I need to do without running Tomcat through Eclipse, I'd be happy to try it.  I never found a good setup for external Tomcat that gave me satisfactory debugging and delta publishing options.

> From: Christopher Schultz [mailto:[hidden email]]
> Sent: Thursday, September 30, 2010 11:44 AM

> 2. Don't put your <Context> in your server.xml. Instead, put it into
>    your webapp's META-INF/context.xml file. Don't have one? Create one.

This is good advice in general, and something I will try to do from now on.  I moved the <Context> elements out of server.xml and into META-INF/context.xml, and everything seems to be working properly.  However, it did not solve my original problem.

I hope to have more time tomorrow to take a more thorough look at what is and isn't happening when I start this server, and why.  Thanks for your help and suggestions.

-August


This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: warning: Setting property 'source' [...] did not find a matching property.

Dwight, August
Well, problem solved.

As I mentioned, the warning disappeared when I got rid of the source attribute in my <Context> element.  My real problem, where Tomcat didn't seem to be publishing my web project, appears to have been caused at least partly by Eclipse adding the src/main/webapp folder to the Java build path.  I could have sworn that I checked for this earlier, but either I didn't actually check or else there was another factor which I never properly identified but somehow fixed at some point.

-August

-----Original Message-----
From: Dwight, August
Sent: Thursday, September 30, 2010 6:23 PM
To: Tomcat Users List
Subject: RE: warning: Setting property 'source' [...] did not find a matching property.

> From: Caldarale, Charles R [mailto:[hidden email]]
> Sent: Thursday, September 30, 2010 1:42 PM
> Subject: RE: warning: Setting property 'source' [...] did not find a matching property.

>> I have no build errors or runtime errors.
>
> Are you looking at *all* of the Tomcat logs when you make that statement?

catalina.*.log and localhost.*.log are both clean.

> What does Tomcat's manager app say about the state of your webapp?
>
> What happens when you run Tomcat by itself, not under Eclipse?

When I run Tomcat by itself, my app works the way it should, and Manager says it's running.

> From: Caldarale, Charles R [mailto:[hidden email]]
> Sent: Thursday, September 30, 2010 12:07 PM>
>
> > From: Christopher Schultz [mailto:[hidden email]]
> > Subject: Re: warning: Setting property 'source' [...] did not find a matching property.
>
> > You're trying to set the "source" attribute on your
> > <Context> element.
>
> Eclipse has the nasty habit of stuffing this illegal attribute there automatically.  Another reason not to > run Tomcat under Eclipse.

If there's a convenient way to do all of the things I need to do without running Tomcat through Eclipse, I'd be happy to try it.  I never found a good setup for external Tomcat that gave me satisfactory debugging and delta publishing options.

> From: Christopher Schultz [mailto:[hidden email]]
> Sent: Thursday, September 30, 2010 11:44 AM

> 2. Don't put your <Context> in your server.xml. Instead, put it into
>    your webapp's META-INF/context.xml file. Don't have one? Create one.

This is good advice in general, and something I will try to do from now on.  I moved the <Context> elements out of server.xml and into META-INF/context.xml, and everything seems to be working properly.  However, it did not solve my original problem.

I hope to have more time tomorrow to take a more thorough look at what is and isn't happening when I start this server, and why.  Thanks for your help and suggestions.

-August


This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...