[jira] [Commented] (INFRA-9383) Change JIRA catalina log to have timestamp

["Mark Thomas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-9383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394828#comment-14394828 ] 

Mark Thomas commented on INFRA-9383:
------------------------------------

Yes that would be lovely. If only it were that easy. The only stuff that appears in catalina.out is what Jira writes to STDOUT rather than to a proper logging system. You really need to raise that with Atlassian. Good luck with that.

Enabling swallowOutput on the Context will help for stdout logging that is generated as part of request processing but not for anything that is generated by one of the many other threads that Jira starts. I'll turn that on this weekend.

>From a logging point of view, you normally get better information in in jira-data/log/atlassian-jira.log, logs/localhost-date.log or catalina-date.log

> Change JIRA catalina log to have timestamp
> ------------------------------------------
>
>                 Key: INFRA-9383
>                 URL: https://issues.apache.org/jira/browse/INFRA-9383
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Geoffrey Corey
>            Priority: Minor
>
> When creating a new project in JIRA, it (again) got into a weird state and needs to be restarted to fix it. When trying to find the cause in the logs, there is no reference for where in the catalina log file to start looking because there is no timestamp. It would be helpful to have that for future debugging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)