Skip to main content
T
TwoEdge
Inspiring
October 4, 2016
Question

"APP1 Segment is too long"

  • October 4, 2016
  • 1 reply
  • 453 views

Hello,

I'm moving an application that has been running on CF 9.0.2 to CF 2016 and am experiencing the following error when using the CFIMAGE tag to convert certain TIFFs  (ranging in size from 1.4mb to 2.5mb):

"APP1 Segment is too long"

More Context from the log:

"

at java.lang.Thread.run(Thread.java:745)

"Error","ajp-nio-8016-exec-9","10/04/16","10:57:05","","APP1 Segment is too long: 1379422"

org.apache.sanselan.formats.jpeg.exifRewrite.ExifRewriter$ExifOverflowException: APP1 Segment is too long: 1379422

  at org.apache.sanselan.formats.jpeg.exifRewrite.ExifRewriter.writeSegmentsReplacingExif(ExifRewriter.java:490)

  at org.apache.sanselan.formats.jpeg.exifRewrite.ExifRewriter.updateExifMetadataLossless(ExifRewriter.java:384)

"

This code has been working fine for many years (literally) on CF 9.x, so I all I am certain of is that it is related to it running on the new server.

Has anyone run into this before? Does anyone have any thoughts, ideas, or suggestions on how to address this issue?

blue skies,

Bryan

This topic has been closed for replies.

1 reply

WolfShade
WolfShade
Legend
October 4, 2016

Hello, TwoEdge​,

You don't mention what you were attempting to do when this error occurred.  Were you trying to upload an image via a form?

Is the web server Apache?  I Googled your error message and found a few links related to Apache.

There are also issues with .GIF metadata related to the error message "APP1 Segment is too long".  Something to do with the marker bits.

If you still have your CF9x server up and running, check all config settings (especially those referring to memory) against your CF2016 CFAdmin.

I hate to sound like a broken record, but it amazes me the number of people who are attempting to upgrade more than one iteration (ie, CF8 to CF10 or CF11; CF9 to CF2016; etc.)  Seems like everyone who does experiences some kind of issue, usually related to tags that are either deprecated or had attributes change.  But, frequently issues like yours also crop up.

HTH,

^_^

T
TwoEdgeAuthor
Inspiring
October 4, 2016

Thanks for the reply.  I figured that this is such a specific error that either someone will have encountered it and know exactly the issue, or (like most) will have no idea.  I also googled the error, but found no help that matches these conditions, especially in the context of ColdFusion.

This is happening after a file upload has been completed, and I think memory is great place for me to focus but so far I am not finding any changes or increases in memory that seem to fix the error. Additionally other files, much larger in size, are having no issues.

I also concur that upgrading from 9.x to 2016 is not ideal to say the least - but it is the only option available and the situation with which I have to deal.

Thanks again.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices