-
Bug
-
Resolution: Timed out
-
Low (View bug fix roadmap)
-
None
-
4.0
-
4
-
2
-
Severity 3 - Minor
-
-
http://localhost:8080/secure/project/AvatarPicker!upload.jspa [500ErrorPage.jsp] Exception caught in 500 page Unexpected block type 0!
javax.imageio.IIOException: Unexpected block type 0!
at com.sun.imageio.plugins.gif.GIFImageReader.readMetadata(GIFImageReader.java:722)
at com.sun.imageio.plugins.gif.GIFImageReader.read(GIFImageReader.java:794)
at javax.imageio.ImageIO.read(ImageIO.java:1422)
at javax.imageio.ImageIO.read(ImageIO.java:1282)
at com.atlassian.core.util.thumbnail.Thumber.getImage(Thumber.java:270)
Some GIF files trigger this bug.
I found a bug report of this error on SUN Bug Database: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6358674
As this is a know bug of Java (since 2005 according to SUN Bug Database), JIRA could better handle this exception and show a more graceful message instead of exploding an exception on the screen!
I'm also attaching a GIF file that triggers the exception.
Workaround
Convert the GIF file to another format like JPEG or PNG.
- is duplicated by
-
JRASERVER-22660 Unable to create thumbnail image for id 12009 from jdog logs
-
- Closed
-
-
JRASERVER-24261 Error on Uploading gif file as project image
-
- Closed
-
- relates to
-
JRASERVER-19557 Thumbnail of certain image attachments fail and cause ERROR in log
-
- Closed
-
[JRASERVER-22011] Exception is thrown when trying to upload GIF file as Avatar
Minimum Version | New: 4 |
Workflow | Original: JAC Bug Workflow v2 [ 2840209 ] | New: JAC Bug Workflow v3 [ 2916742 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2590278 ] | New: JAC Bug Workflow v2 [ 2840209 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1521476 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2590278 ] |
Current Status |
Original:
{panel:title=Atlassian Update – 16 November 2017|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff}
Hi everyone, The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low. Jira team is focusing on [bigger and more impactful issues at the moment|https://jira.atlassian.com/secure/RapidView.jspa?rapidView=2290&tab=filter] and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as *Timed Out*. Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster. {panel} |
New:
{panel:title=Atlassian Update – 16 November 2017|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff}
Hi everyone, The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low. Jira team is focusing on [bigger and more impactful issues at the moment|https://jira.atlassian.com/secure/RapidBoard.jspa?rapidView=2290] and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as *Timed Out*. Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster. {panel} |
Resolution | New: Timed out [ 10 ] | |
Status | Original: Verified [ 10005 ] | New: Resolved [ 5 ] |
Current Status |
New:
{panel:title=Atlassian Update – 16 November 2017|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff}
Hi everyone, The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low. Jira team is focusing on [bigger and more impactful issues at the moment|https://jira.atlassian.com/secure/RapidView.jspa?rapidView=2290&tab=filter] and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as *Timed Out*. Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster. {panel} |
|
Labels | Original: affects-server | New: affects-server low-interest obsolete old-affect-version |
Labels | New: affects-server |
Support reference count | New: 2 |