Repeatedly debug messaged from X509ServletFilterBase

cancel
Showing results for 
Search instead for 
Did you mean: 
Active Member II

Repeatedly debug messaged from X509ServletFilterBase

Jump to solution

We are trying to upgrade from 5.0 to 2017-04 edition.

Among other errors we get the above debug message:

2017-07-18 16:25:01,062  DEBUG [scripts.servlet.X509ServletFilterBase] [http-bio-127.0.0.1-8443-exec-5] Enforcing X509 request
2017-07-18 16:25:01,063  DEBUG [scripts.servlet.X509ServletFilterBase] [http-bio-127.0.0.1-8443-exec-5] Checking cert is valid
2017-07-18 16:25:01,063  DEBUG [scripts.servlet.X509ServletFilterBase] [http-bio-127.0.0.1-8443-exec-5] Cert is valid

It is unstopably repeated, filling our logs. Any ideas why this happens?

Thanks in advance.

1 Solution

Accepted Solutions
Master

Re: Repeatedly debug messaged from X509ServletFilterBase

Jump to solution

You should configure the log level via custom-log4j.properties to a higher level for the X509ServletFilterBase class. Apparently it is set to DEBUG and that is why you are seeing many messages. Generally, you should never have DEBUG enabled on an acceptance / production environment (except for specific short issue debug phases when the issue cannot be reproduced elsewhere). DEBUG is supposed to be used for development / test environments.

View solution in original post

2 Replies
Master

Re: Repeatedly debug messaged from X509ServletFilterBase

Jump to solution

You should configure the log level via custom-log4j.properties to a higher level for the X509ServletFilterBase class. Apparently it is set to DEBUG and that is why you are seeing many messages. Generally, you should never have DEBUG enabled on an acceptance / production environment (except for specific short issue debug phases when the issue cannot be reproduced elsewhere). DEBUG is supposed to be used for development / test environments.

View solution in original post

Active Member II

Re: Repeatedly debug messaged from X509ServletFilterBase

Jump to solution

we added to tomcat/shared/classes/alfresco/extension/custom-log4j.properties

log4j.logger.org.alfresco.web.scripts.servlet=warn

thank you