Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlValidation' to 'false' did not find a matching property.

Klas Mellbourn April 23, 2013

In the log stash-stderr log I get the following two warnings about [SetPropertiesRule]

Apr 19, 2013 9:32:54 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\atlassian-stash\lib\native;D:\stash\lib\native
Apr 19, 2013 9:32:54 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlValidation' to 'false' did not find a matching property.
Apr 19, 2013 9:32:54 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlNamespaceAware' to 'false' did not find a matching property.
Apr 19, 2013 9:32:55 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-7990"]
Apr 19, 2013 9:32:55 AM org.apache.catalina.startup.Catalina load

We are using Atlassian Stash v2.1.2.

The webserver seems to work well generally, but I do have a problem that I have reported in another post.

How should I adress these warnings? Can I ignore them?

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
cofarrell
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 23, 2013

Hi Klass,

It's certainly nothing to worry about. Unfortunately that's expected (and probably shouldn't be a warning from Tomcat). I believe what is happening is that Tomcat configuration we are shipping with is referencing a deprecated property and is being ignored. I might see if we can do something about it, but I would strongly suggest leaving it as it is for now.

Honestly, unless something goes catastrophically wrong, the logs you're really interested in will be in $STASH_HOME/log, which are far more important.

Cheers,

Charles

Klas Mellbourn April 23, 2013

Good to know what logs are priorotized.

There are so many that I've made a script to display them all :)

cofarrell
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 23, 2013

Well I'm not sure prioritized is the word I would use, they just have different purposes. :)

The catalina.out logs, which contain the warning above, are purely about Tomcat. The $STASH_HOME/log files are written by Stash. In that directory each file has a different purpose so that we can find specific information when required. The atlassian-stash-access.log contains http and ssh requests only (which might be relevant to your other question about broken connections), whereas the atlassian-stash.log is for error and information messages.

Charles

TAGS
AUG Leaders

Atlassian Community Events