Corrupted images?

[jabain]

Hi All,

We have been experiencing sporatic corrupted images when uploading images from the iPads. The users are on IOS8.1.1 and 8.1.2. iSeries is at V7R1.

Our application has no local storage. Everything is online only.

Has anyone encountered this before? Any thoughts on what to check?

Regards,

Andy

[tsupartono]

Can you tell us the type of back-end you're using (LANSA or aXes)?
Do you use SSL?
Do the data corruptions occur more often with bigger images (compared to small images)?

[jabain]

Thank you for your response...

We are using LANSA backend with SSL.
The images are pretty much the same size. They are created by signatures boxes on the screen. The percent of corruptions is pretty small maybe 5%.

I kind of suspect that the issue is due to poor cell reception, but the users have not reported any errors when posting the screen. I would assume that if the cell connection dropped during the http post, that the LongRange client would have given an error.

Andy

[tsupartono]

Hi,
There are known data corruption issues with connecting to Apache on IBM i with SSL since iOS 8
We are currently investigating this.

[tsupartono]

What version of LANSA are you using on the back-end (V12 or V13)?

[jabain]

We are using V12 on the back end.

Is there any workaround for the known issue?

[tsupartono]

Hi Andy,
We need to determine first if the corruption issue is indeed the SSL corruption issue.
With the SSL corruption issue, generally the whole data stream would get corrupted and you should get an "internal server error" from LANSA back-end as it tries to parse the corrupted incoming data stream. If it's only the pictures that get corrupted, this might indicate that it could be a different problem.

If possible you can also turn SSL off temporarily to see if this fixes the issue.

I think it's best if we handle this through LANSA Support.
Can you log this with Support, please also include the URL to this forum entry.

Thanks.

[tsupartono]

Additional info on this.

1) SSL corruption issue can be fixed by upgrading your LANSA back-end to V13.
2) Make sure Apache is set to use SSL Version 3.0 ONLY.
3) The latest client software (build 1.0.6.870) must be used when connecting to LANSA V13.

[jabain]

Thanks for your assistance. I am now working with LANSA Support to get the pieces up to the newest version.

Andy