com.atlassian.jira.issue.attachment.NoAttachmentDataException: Attachment does not exist in filesystem /data/home/jadmin_x/ubk-test-7.0.9/home/data/attachments/BXITAFW/10000/BXITAFW-1341/160940

Atlassian JIRA | Dieter Greiner | 10 months ago
  1. 0

    Hi Atlassian, Would it be possible to omit the stack trace in the warning {code} 2016-01-21 18:09:19,896 SupportHealthCheckThread-7 WARN ServiceRunner [c.a.j.p.healthcheck.support.AttachmentHealthCheck] There was a RuntimeException when testing the attachment {0} com.atlassian.jira.issue.attachment.NoAttachmentDataException: Attachment does not exist in filesystem /data/home/jadmin_x/ubk-test-7.0.9/home/data/attachments/BXITAFW/10000/BXITAFW-1341/160940 at com.atlassian.jira.issue.attachment.store.DefaultFileSystemAttachmentStore.getAttachmentData(DefaultFileSystemAttachmentStore.java:143) at com.atlassian.jira.issue.attachment.store.DefaultFileSystemAttachmentStore.getAttachment(DefaultFileSystemAttachmentStore.java:125) at com.atlassian.jira.issue.attachment.store.BackwardCompatibleStoreAdapter.getAttachment(BackwardCompatibleStoreAdapter.java:97) at com.atlassian.jira.issue.attachment.BackwardCompatibleAttachmentStore.getAttachment(BackwardCompatibleAttachmentStore.java:163) at com.atlassian.jira.issue.attachment.BackwardCompatibleAttachmentStore.getAttachment(BackwardCompatibleAttachmentStore.java:209) at com.atlassian.jira.issue.managers.DefaultAttachmentManager.streamAttachmentContent(DefaultAttachmentManager.java:725) ... 3 filtered at java.lang.reflect.Method.invoke(Method.java:497) at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:30) at com.sun.proxy.$Proxy347.streamAttachmentContent(Unknown Source) ... 3 filtered at java.lang.reflect.Method.invoke(Method.java:497) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56) at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133) at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70) at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133) at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) at com.sun.proxy.$Proxy2077.streamAttachmentContent(Unknown Source) {code} when a attachment cannot be found and just log the missing attachment ? It would also be great to see the list of missing attachments in the UI or at least only the first 5 or 10 of them. The stack traces clutter our log files with non relevant information that makes it more difficult to see real errors. Also on our test systems which are copies of production system we usually don't have attachments and there this situation is even normal.

    Atlassian JIRA | 10 months ago | Dieter Greiner
    com.atlassian.jira.issue.attachment.NoAttachmentDataException: Attachment does not exist in filesystem /data/home/jadmin_x/ubk-test-7.0.9/home/data/attachments/BXITAFW/10000/BXITAFW-1341/160940
  2. 0

    Hi Atlassian, Would it be possible to omit the stack trace in the warning {code} 2016-01-21 18:09:19,896 SupportHealthCheckThread-7 WARN ServiceRunner [c.a.j.p.healthcheck.support.AttachmentHealthCheck] There was a RuntimeException when testing the attachment {0} com.atlassian.jira.issue.attachment.NoAttachmentDataException: Attachment does not exist in filesystem /data/home/jadmin_x/ubk-test-7.0.9/home/data/attachments/BXITAFW/10000/BXITAFW-1341/160940 at com.atlassian.jira.issue.attachment.store.DefaultFileSystemAttachmentStore.getAttachmentData(DefaultFileSystemAttachmentStore.java:143) at com.atlassian.jira.issue.attachment.store.DefaultFileSystemAttachmentStore.getAttachment(DefaultFileSystemAttachmentStore.java:125) at com.atlassian.jira.issue.attachment.store.BackwardCompatibleStoreAdapter.getAttachment(BackwardCompatibleStoreAdapter.java:97) at com.atlassian.jira.issue.attachment.BackwardCompatibleAttachmentStore.getAttachment(BackwardCompatibleAttachmentStore.java:163) at com.atlassian.jira.issue.attachment.BackwardCompatibleAttachmentStore.getAttachment(BackwardCompatibleAttachmentStore.java:209) at com.atlassian.jira.issue.managers.DefaultAttachmentManager.streamAttachmentContent(DefaultAttachmentManager.java:725) ... 3 filtered at java.lang.reflect.Method.invoke(Method.java:497) at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:30) at com.sun.proxy.$Proxy347.streamAttachmentContent(Unknown Source) ... 3 filtered at java.lang.reflect.Method.invoke(Method.java:497) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56) at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133) at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70) at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133) at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) at com.sun.proxy.$Proxy2077.streamAttachmentContent(Unknown Source) {code} when a attachment cannot be found and just log the missing attachment ? It would also be great to see the list of missing attachments in the UI or at least only the first 5 or 10 of them. The stack traces clutter our log files with non relevant information that makes it more difficult to see real errors. Also on our test systems which are copies of production system we usually don't have attachments and there this situation is even normal.

    Atlassian JIRA | 10 months ago | Dieter Greiner
    com.atlassian.jira.issue.attachment.NoAttachmentDataException: Attachment does not exist in filesystem /data/home/jadmin_x/ubk-test-7.0.9/home/data/attachments/BXITAFW/10000/BXITAFW-1341/160940

    Root Cause Analysis

    1. com.atlassian.jira.issue.attachment.NoAttachmentDataException

      Attachment does not exist in filesystem /data/home/jadmin_x/ubk-test-7.0.9/home/data/attachments/BXITAFW/10000/BXITAFW-1341/160940

      at com.atlassian.jira.issue.attachment.store.DefaultFileSystemAttachmentStore.getAttachmentData()
    2. com.atlassian.jira
      DefaultAttachmentManager.streamAttachmentContent
      1. com.atlassian.jira.issue.attachment.store.DefaultFileSystemAttachmentStore.getAttachmentData(DefaultFileSystemAttachmentStore.java:143)
      2. com.atlassian.jira.issue.attachment.store.DefaultFileSystemAttachmentStore.getAttachment(DefaultFileSystemAttachmentStore.java:125)
      3. com.atlassian.jira.issue.attachment.store.BackwardCompatibleStoreAdapter.getAttachment(BackwardCompatibleStoreAdapter.java:97)
      4. com.atlassian.jira.issue.attachment.BackwardCompatibleAttachmentStore.getAttachment(BackwardCompatibleAttachmentStore.java:163)
      5. com.atlassian.jira.issue.attachment.BackwardCompatibleAttachmentStore.getAttachment(BackwardCompatibleAttachmentStore.java:209)
      6. com.atlassian.jira.issue.managers.DefaultAttachmentManager.streamAttachmentContent(DefaultAttachmentManager.java:725)
      6 frames