com.atlassian.core.AtlassianCoreException

Error in action: com.atlassian.jira.action.attachment.AttachmentCreate@e61897, result: error You must specify a filename and mime type

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web30

  • via Atlassian JIRA by Matt Adair, 1 year ago
    Error in action: com.atlassian.jira.action.attachment.AttachmentCreate@e61897, result: error You must specify a filename and mime type
  • via Atlassian JIRA by Matt Adair, 11 months ago
    Error in action: com.atlassian.jira.action.attachment.AttachmentCreate@e61897, result: error You must specify a filename and mime type
  • via Atlassian JIRA by Nick Minutello, 11 months ago
    Error in action: com.atlassian.jira.action.issue.IssueDelete@157f3a4, result: null
  • Stack trace

    • com.atlassian.core.AtlassianCoreException: Error in action: com.atlassian.jira.action.attachment.AttachmentCreate@e61897, result: error You must specify a filename and mime type at com.atlassian.core.action.ActionUtils.checkForErrors(ActionUtils.java:53) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.createAttachmentWithPart(AbstractMessageHandler.java:88) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.createAttachmentsForMessage(AbstractMessageHandler.java:61) at com.atlassian.jira.service.util.handler.FullCommentHandler.handleMessage(FullCommentHandler.java:64) at com.atlassian.jira.service.services.pop.PopService.run(PopService.java:97) at com.atlassian.jira.service.JiraServiceContainer.run(JiraServiceContainer.java:54) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:53) at org.quartz.core.JobRunShell.run(JobRunShell.java:147) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:387)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.