java.io.UnsupportedEncodingException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • When JIRA is configured to parse incoming mails (from POP/IMAP) to create new issues, it will go into a loop repeatedly creating issues if the email attachment cannot be parsed. For instance, if an email's attachment has an encoding Java doesn't support (eg. utf-7 - see JRA-5812), then JIRA loops, creating an issue and then failing to clear it because the attachment isn't processed. 2007-01-31 12:49:34,206 JiraQuartzScheduler_Worker-0 WARN [jira.issue.managers.DefaultAttachmentManager] Cannot create attachment without a filename - inline content? See http://jira.atlassian.com/browse/JRA-10825 (file=tempattach30736dat). 2007-01-31 12:49:34,208 JiraQuartzScheduler_Worker-0 ERROR [service.util.handler.CreateIssueHandler] Could not create issue! java.io.UnsupportedEncodingException: unicode-1-1-utf-7 at sun.nio.cs.StreamDecoder.forInputStreamReader(StreamDecoder.java:52) at java.io.InputStreamReader.<init>(InputStreamReader.java:83) at com.sun.mail.handlers.text_plain.getContent(text_plain.java:64) at javax.activation.DataSourceDataContentHandler.getContent(DataHandler.java:774) at javax.activation.DataHandler.getContent(DataHandler.java:521) at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:603) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.handleMultipart(AbstractMessageHandler.java:236) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.createAttachmentsForMessage(AbstractMessageHandler.java:201) at com.atlassian.jira.service.util.handler.CreateIssueHandler.handleMessage(CreateIssueHandler.java:201) at com.atlassian.jira.service.util.handler.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:115) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:190) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) 2007-01-31 12:51:34,224 JiraQuartzScheduler_Worker-3 WARN [jira.issue.managers.DefaultAttachmentManager] Cannot create attachment without a filename - inline content? See http://jira.atlassian.com/browse/JRA-10825 (file=tempattach30737dat). 2007-01-31 12:51:34,226 JiraQuartzScheduler_Worker-3 ERROR [service.util.handler.CreateIssueHandler] Could not create issue! java.io.UnsupportedEncodingException: unicode-1-1-utf-7 at sun.nio.cs.StreamDecoder.forInputStreamReader(StreamDecoder.java:52) at java.io.InputStreamReader.<init>(InputStreamReader.java:83) at com.sun.mail.handlers.text_plain.getContent(text_plain.java:64) at javax.activation.DataSourceDataContentHandler.getContent(DataHandler.java:774) at javax.activation.DataHandler.getContent(DataHandler.java:521) at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:603) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.handleMultipart(AbstractMessageHandler.java:236) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.createAttachmentsForMessage(AbstractMessageHandler.java:201) at com.atlassian.jira.service.util.handler.CreateIssueHandler.handleMessage(CreateIssueHandler.java:201) at com.atlassian.jira.service.util.handler.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:115) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:190) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
    via by Dylan Etkin [Atlassian],
  • When JIRA is configured to parse incoming mails (from POP/IMAP) to create new issues, it will go into a loop repeatedly creating issues if the email attachment cannot be parsed. For instance, if an email's attachment has an encoding Java doesn't support (eg. utf-7 - see JRA-5812), then JIRA loops, creating an issue and then failing to clear it because the attachment isn't processed. 2007-01-31 12:49:34,206 JiraQuartzScheduler_Worker-0 WARN [jira.issue.managers.DefaultAttachmentManager] Cannot create attachment without a filename - inline content? See http://jira.atlassian.com/browse/JRA-10825 (file=tempattach30736dat). 2007-01-31 12:49:34,208 JiraQuartzScheduler_Worker-0 ERROR [service.util.handler.CreateIssueHandler] Could not create issue! java.io.UnsupportedEncodingException: unicode-1-1-utf-7 at sun.nio.cs.StreamDecoder.forInputStreamReader(StreamDecoder.java:52) at java.io.InputStreamReader.<init>(InputStreamReader.java:83) at com.sun.mail.handlers.text_plain.getContent(text_plain.java:64) at javax.activation.DataSourceDataContentHandler.getContent(DataHandler.java:774) at javax.activation.DataHandler.getContent(DataHandler.java:521) at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:603) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.handleMultipart(AbstractMessageHandler.java:236) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.createAttachmentsForMessage(AbstractMessageHandler.java:201) at com.atlassian.jira.service.util.handler.CreateIssueHandler.handleMessage(CreateIssueHandler.java:201) at com.atlassian.jira.service.util.handler.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:115) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:190) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) 2007-01-31 12:51:34,224 JiraQuartzScheduler_Worker-3 WARN [jira.issue.managers.DefaultAttachmentManager] Cannot create attachment without a filename - inline content? See http://jira.atlassian.com/browse/JRA-10825 (file=tempattach30737dat). 2007-01-31 12:51:34,226 JiraQuartzScheduler_Worker-3 ERROR [service.util.handler.CreateIssueHandler] Could not create issue! java.io.UnsupportedEncodingException: unicode-1-1-utf-7 at sun.nio.cs.StreamDecoder.forInputStreamReader(StreamDecoder.java:52) at java.io.InputStreamReader.<init>(InputStreamReader.java:83) at com.sun.mail.handlers.text_plain.getContent(text_plain.java:64) at javax.activation.DataSourceDataContentHandler.getContent(DataHandler.java:774) at javax.activation.DataHandler.getContent(DataHandler.java:521) at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:603) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.handleMultipart(AbstractMessageHandler.java:236) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.createAttachmentsForMessage(AbstractMessageHandler.java:201) at com.atlassian.jira.service.util.handler.CreateIssueHandler.handleMessage(CreateIssueHandler.java:201) at com.atlassian.jira.service.util.handler.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:115) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:190) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
    via by Dylan Etkin [Atlassian],
  • java.io.UnsupportedEncodingException
    via Stack Overflow by user2133558
    ,
  • My FogBugz import failed and this is shown on the top of the page: FogBugz import completed with errors The importer has completed with some errors. You can find the errors in the logs below by searching for lines which begin with FAILED. It is likely that the import was not correctly configured. The text "It is likely that the import was not correctly configured." should read "It is possible that the import was not correctly configured.". But really, it should check what type of exceptions were generated and handle it accordingly. Ideally a link to Atlassian's own JIRA installation searching on the exceptions would be user friendly and relatively easy to implement. The exception I actually got was [08:59:50] Only new Issues will be imported [09:02:08] FAILED: Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state [09:02:08] com.atlassian.jira.external.ExternalRuntimeException: java.io.UnsupportedEncodingException: geostd8 at com.atlassian.jira.external.ExternalUtils.getTextDataFromMimeMessage(ExternalUtils.java:922) at com.atlassian.jira.imports.fogbugz.transformer.CommentTransformer.transform(CommentTransformer.java:48) at com.atlassian.jira.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:271) at com.atlassian.jira.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:252) at com.atlassian.jira.imports.fogbugz.transformer.IssueTransformer.transform(IssueTransformer.java:208) at com.atlassian.jira.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:271) at com.atlassian.jira.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:252) at com.atlassian.jira.imports.fogbugz.FogBugzDataBean.getIssues(FogBugzDataBean.java:65) at com.atlassian.jira.imports.fogbugz.FogBugzDataBean.getIssuesIterator(FogBugzDataBean.java:70) at com.atlassian.jira.imports.importer.impl.DefaultJiraDataImporter.importIssues(DefaultJiraDataImporter.java:430) at com.atlassian.jira.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:120) at com.atlassian.jira.imports.importer.impl.ImporterThread.run(ImporterThread.java:21) Caused by: java.io.UnsupportedEncodingException: geostd8 at sun.nio.cs.StreamDecoder.forInputStreamReader(Unknown Source) at java.io.InputStreamReader.<init>(Unknown Source) at com.sun.mail.handlers.text_plain.getContent(text_plain.java:64) at javax.activation.DataSourceDataContentHandler.getContent(Unknown Source) at javax.activation.DataHandler.getContent(Unknown Source) at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:603) at com.atlassian.jira.external.ExternalUtils.getCleanedContent(ExternalUtils.java:956) at com.atlassian.jira.external.ExternalUtils.getTextDataFromMimeMessage(ExternalUtils.java:938) at com.atlassian.jira.external.ExternalUtils.getTextDataFromMimeMessage(ExternalUtils.java:918) Which is JIRA missing an encoding and not a configuration problem and not a user error. It's also something JIRA could easily clean up and present to the user in a friendly way (i.e., "Case ID's x, y, and z where not imported because their attachments use encoding geostd8 and that encoding is not supported. To search Atlassian's support for information on adding adding this encoding _click here_."
    via by Samuel R. Neff,
  • My FogBugz import failed and this is shown on the top of the page: FogBugz import completed with errors The importer has completed with some errors. You can find the errors in the logs below by searching for lines which begin with FAILED. It is likely that the import was not correctly configured. The text "It is likely that the import was not correctly configured." should read "It is possible that the import was not correctly configured.". But really, it should check what type of exceptions were generated and handle it accordingly. Ideally a link to Atlassian's own JIRA installation searching on the exceptions would be user friendly and relatively easy to implement. The exception I actually got was [08:59:50] Only new Issues will be imported [09:02:08] FAILED: Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state [09:02:08] com.atlassian.jira.external.ExternalRuntimeException: java.io.UnsupportedEncodingException: geostd8 at com.atlassian.jira.external.ExternalUtils.getTextDataFromMimeMessage(ExternalUtils.java:922) at com.atlassian.jira.imports.fogbugz.transformer.CommentTransformer.transform(CommentTransformer.java:48) at com.atlassian.jira.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:271) at com.atlassian.jira.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:252) at com.atlassian.jira.imports.fogbugz.transformer.IssueTransformer.transform(IssueTransformer.java:208) at com.atlassian.jira.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:271) at com.atlassian.jira.web.action.util.DatabaseConnectionBean.queryDb(DatabaseConnectionBean.java:252) at com.atlassian.jira.imports.fogbugz.FogBugzDataBean.getIssues(FogBugzDataBean.java:65) at com.atlassian.jira.imports.fogbugz.FogBugzDataBean.getIssuesIterator(FogBugzDataBean.java:70) at com.atlassian.jira.imports.importer.impl.DefaultJiraDataImporter.importIssues(DefaultJiraDataImporter.java:430) at com.atlassian.jira.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:120) at com.atlassian.jira.imports.importer.impl.ImporterThread.run(ImporterThread.java:21) Caused by: java.io.UnsupportedEncodingException: geostd8 at sun.nio.cs.StreamDecoder.forInputStreamReader(Unknown Source) at java.io.InputStreamReader.<init>(Unknown Source) at com.sun.mail.handlers.text_plain.getContent(text_plain.java:64) at javax.activation.DataSourceDataContentHandler.getContent(Unknown Source) at javax.activation.DataHandler.getContent(Unknown Source) at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:603) at com.atlassian.jira.external.ExternalUtils.getCleanedContent(ExternalUtils.java:956) at com.atlassian.jira.external.ExternalUtils.getTextDataFromMimeMessage(ExternalUtils.java:938) at com.atlassian.jira.external.ExternalUtils.getTextDataFromMimeMessage(ExternalUtils.java:918) Which is JIRA missing an encoding and not a configuration problem and not a user error. It's also something JIRA could easily clean up and present to the user in a friendly way (i.e., "Case ID's x, y, and z where not imported because their attachments use encoding geostd8 and that encoding is not supported. To search Atlassian's support for information on adding adding this encoding _click here_."
    via by Samuel R. Neff,
    • java.io.UnsupportedEncodingException: unicode-1-1-utf-7 at sun.nio.cs.StreamDecoder.forInputStreamReader(StreamDecoder.java:52) at java.io.InputStreamReader.<init>(InputStreamReader.java:83) at com.sun.mail.handlers.text_plain.getContent(text_plain.java:64) at javax.activation.DataSourceDataContentHandler.getContent(DataHandler.java:774) at javax.activation.DataHandler.getContent(DataHandler.java:521) at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:603) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.handleMultipart(AbstractMessageHandler.java:236) at com.atlassian.jira.service.util.handler.AbstractMessageHandler.createAttachmentsForMessage(AbstractMessageHandler.java:201) at com.atlassian.jira.service.util.handler.CreateIssueHandler.handleMessage(CreateIssueHandler.java:201) at com.atlassian.jira.service.util.handler.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:115) at com.atlassian.jira.service.services.mail.MailFetcherService.run(MailFetcherService.java:190) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191)

    Users with the same issue

    Unknown visitor
    Unknown visitor1 times, last one,
    serious2monkeysserious2monkeys
    589 times, last one,
    rprp
    1 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    HronomHronom
    19 times, last one,
    1 more bugmates