[
https://issues.apache.org/jira/browse/ACE-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763158#action_12763158
]
Toni Menzel commented on ACE-35:
--------------------------------
Whats the overall idea on this?
I looked for example at LogSyncTask in gateway.
Here we could do:
a.) lower severity to INFO and set default level of log output to WARN
b.) print message exactly once and supress this message until
end-of-try/catch-block has been reached again (the reset a flag parameter or so)
c.) because this is a task, maybe change task scheduling if it fails, so it
does not try to sync every second but every minute if it was unsuccessful. This
of cause can and must be solved on a higher level. Should be done by the
scheduler then.
so, what do you want, a b or c (or d) ?
Same for ACE-37 and the other CLONES.
> Using the file based server, a gateway will complain too much about not being
> able to connect to an audit log.
> --------------------------------------------------------------------------------------------------------------
>
> Key: ACE-35
> URL: https://issues.apache.org/jira/browse/ACE-35
> Project: Ace
> Issue Type: Bug
> Reporter: Marcel Offermans
>
> As explained in the documentation, a gateway that is connected to the file
> based server, complains every few seconds about not being able to connect to
> an audit log. That should be fixed, as these messages are more annoying than
> useful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
