[
https://jira.jboss.org/jira/browse/TEIID-20?page=com.atlassian.jira.plugi...
]
Steven Hawkins resolved TEIID-20.
---------------------------------
Fix Version/s: 6.2.0
(was: 6.3.0)
Resolution: Out of Date
Control of audit logging is now directly in the hands of the user via the
log4j.properties. Setting the audit context to a rolling file appender will achieve the
intent of this issue.
Audit logs should roll-over (not just grow)
-------------------------------------------
Key: TEIID-20
URL:
https://jira.jboss.org/jira/browse/TEIID-20
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 6.1.0
Reporter: Paul Nittel
Fix For: 6.2.0
Defect Tracker #16477: At present, the audit logs continue to grow until the server is
shut down and restarted. At that time, it either creates a new file or appends to the
current file.
The audit logs should roll-over in the same manner as the process logs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira