#log4j.xml #logginglevels
Hi guys!
My view.log is basically a really long list of DBDrive lines, for example
2017/10/25 18.35.12.006 INFO [Rule Action Executor-2] [CreateEiamUserAction] EIAM is using an external directory, no global user will be added/changed/removed
2017/10/25 18.35.12.006 INFO [http-bio-8080-exec-20] [DBDriver] DB-17 | Query: select * from usm_request_auto_delegation where delegator_id = ? AND delegation_type = ?
2017/10/25 18.35.12.006 INFO [http-bio-8080-exec-10] [DBDriver] DB-21 | Query: select * from usm_request_auto_delegation where delegator_id = ? AND delegation_type = ?
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-6] [DBDriver] DB-23 | Query values: [f3135606, 1]
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-6] [DBDriver] DB-23 | Rows=0
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-20] [DBDriver] DB-17 | Query values: [f3306375, 1]
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-20] [DBDriver] DB-17 | Rows=0
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-10] [DBDriver] DB-21 | Query values: [f2981079, 0]
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-16] [DBDriver] DB-22 | Query: select * from usm_request_auto_delegation where delegator_id = ? AND delegation_type = ?
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-10] [DBDriver] DB-21 | Rows=0
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-10] [DBDriver] DB-21 | Query: select * from usm_request_auto_delegation where delegator_id = ? AND delegation_type = ?
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-16] [DBDriver] DB-22 | Query values: [f0382459, 0]
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-16] [DBDriver] DB-22 | Rows=0
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-10] [DBDriver] DB-21 | Query values: [f2981079, 1]
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-10] [DBDriver] DB-21 | Rows=0
2017/10/25 18.35.12.022 INFO [http-bio-8080-exec-16] [DBDriver] DB-22 | Query: select * from usm_request_auto_delegation where delegator_id = ? AND delegation_type = ?
2017/10/25 18.35.12.037 INFO [http-bio-8080-exec-16] [DBDriver] DB-22 | Query values: [f0382459, 1]
2017/10/25 18.35.12.037 INFO [http-bio-8080-exec-16] [DBDriver] DB-22 | Rows=0
And ActiveMQ Session
2017/10/25 18.35.11.959 INFO [ActiveMQ Session Task-8] [DBDriver] DB-20 | Rows=1
2017/10/25 18.35.11.975 INFO [ActiveMQ Session Task-8] [DBDriver] DB-20 | Query: select * from usm_rule_action a, usm_rule b where a.rule_id=b.rule_id and a.status=1 and b.status=1 and rule_action_id=?
2017/10/25 18.35.11.975 INFO [ActiveMQ Session Task-8] [DBDriver] DB-20 | Query values: [USER_MODIFY_UPDATE_EIAM]
2017/10/25 18.35.11.975 INFO [ActiveMQ Session Task-8] [DBDriver] DB-20 | Rows=1
I know that I can raise root to WARN and all this would be over, but I don't know if the INFO is really necessary
Is there a reason to use the INFO log level in production environment?
This KB enable catalog's TRACE ( or DEBUG ) level for diagnosing purpose,
shows how to lower the level, saying that the default is INFO, but does service catalog for any reason needs this level?