Search

1 to 2 of 2
Sort by

Discussion Post
How to disable DBDriver and ActiveMQ from view.log?

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?


Discussion Thread 3
How to disable DBDriver and ActiveMQ from view.log?

Focus Search - 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?