Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-66226

Attachment warning message in log file



    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 7.5.0, 7.6.0, 7.7.0, 7.8.0, 7.10.1, 7.13.0, 7.13.1, 7.12.3, 8.2.2, 8.6.1
    • Issue - Attachments
    • None



      There are some warning messages in the log file when adding an attachment to a JIRA issue.

      Steps to Reproduce

      1. Take a printscreen or copy a picture into memory; Ctrl+c.
      2. Navigate to issue view screen in JIRA.
      3. Press Ctrl+v, Attach screenshot window should pop up.
      4. Click on "Upload".

      Expected Results

      Attachment is added and no warning messages in the log file.

      Actual Results

      Attachment is added, but you get a series of warnings in atlassian-jira.log file:

      2017-10-29 10:09:19,123 http-nio-8750-exec-25 WARN admin 609x5002x1 1x9am3h xx.xx.xx.xx /secure/ShowAttachScreenshotFormAction.jspa [c.a.j.w.a.issue.util.BackwardCompatibleTemporaryAttachmentUtil] Using deprecated method for adding attachments to issue! Someone still uses TemporaryAttachmentsMonitor - you can probably track him by looking at the referrer or previous requests to JIRA.
      2017-10-29 10:09:19,145 http-nio-8750-exec-25 WARN admin 609x5002x1 1x9am3h xx.xx.xx.xx /secure/ShowAttachScreenshotFormAction.jspa [c.a.j.issue.managers.DefaultAttachmentManager] Temporary attachment missing: 8390060816817697834
      2017-10-29 10:09:19,175 http-nio-8750-exec-25 WARN admin 609x5002x1 1x9am3h xx.xx.xx.xx /secure/ShowAttachScreenshotFormAction.jspa [c.a.j.issue.fields.AttachmentSystemField] There were errors while converting temporary attachments: AttachmentError{logMessage='Temporary attachment missing: 8390060816817697834', localizedMessage='Unable to find temporary attachment.', filename='#8390060816817697834', reason=VALIDATION_FAILED, exception=none()}

      Workaround - Temporary

      This is useful when you want to see if the problem is resolved, or can't afford an application restart:

      • Go to Jira Admin > Logging and Profiling
      • Click "Configure logging level for another package"
      • Add each class name shown below, with the level set to ERROR

      Workaround - Permanent

      You can add the following to $jira-install/atlassian-jira/WEB-INF/classes/log4j.properties - and restart Jira.

      # Reduce Log Spam from https://jira.atlassian.com/browse/JRASERVER-66226 when folks paste attachments in:
      log4j.logger.com.atlassian.jira.web.action.issue.util.BackwardCompatibleTemporaryAttachmentUtil = ERROR, console, filelog
      log4j.additivity.com.atlassian.jira.web.action.issue.util.BackwardCompatibleTemporaryAttachmentUtil = false
      log4j.logger.com.atlassian.jira.issue.managers.DefaultAttachmentManager = ERROR, console, filelog
      log4j.additivity.com.atlassian.jira.issue.managers.DefaultAttachmentManager = false
      log4j.logger.com.atlassian.jira.issue.fields.AttachmentSystemField = ERROR, console, filelog
      log4j.additivity.com.atlassian.jira.issue.fields.AttachmentSystemField = false


        Issue Links



              Unassigned Unassigned
              mmuthusamy Moga
              76 Vote for this issue
              60 Start watching this issue