parmelim
(Pedro Armelim)
September 6, 2017, 2:56pm
#1
Hi
I’ve just updated a few projects to latest 6.6 version and I have a big problem.
Images (by your samples) are not showed in the embedded fields, just the upper part is showed.
Like file corruption, wich is not, just checked, filestorages are ok.
If I try to download I get the error in the image, where you also see the part of the image that was loaded when edit screen was opened.
That does not happen in Studio development, so I went ahead and updated some apps in production.
Thanks,
Pedro
1 Like
krivopustov
(Konstantin Krivopustov)
September 6, 2017, 3:33pm
#2
Hi Pedro,
What application server do you use and what version? How do you deploy the app (exploded WARs, WARs, single WAR, etc.)?
parmelim
(Pedro Armelim)
September 6, 2017, 4:29pm
#3
Hi Konstantin
Apache Tomcat on Centos 7.
I deploy 2 WARs .war and -core.war.
This was functioning well on Cuba 6.5
parmelim
(Pedro Armelim)
September 6, 2017, 5:14pm
#4
It’s Apache Tomcat 8.5.5 on Centos 7, forgot the Tomcat version
krivopustov
(Konstantin Krivopustov)
September 6, 2017, 6:01pm
#5
I would suggest upgrading to the latest Tomcat 8.5 (at least to 8.5.14 which we use) before any further investigation.
parmelim
(Pedro Armelim)
September 6, 2017, 9:45pm
#6
Hi Konstantin
I did exactly that, thanks for mentioning the upgrade.
I upgraded to 8.5.20, latest version, whith best hopes.
But I have exactly the same problem.
krivopustov
(Konstantin Krivopustov)
September 7, 2017, 4:54am
#7
OK. Could you share the code of loading images?
artamonov
(Yuriy Artamonov)
September 7, 2017, 7:18am
#8
Hi,
We’ve found that these changes https://youtrack.cuba-platform.com/issue/PL-9458 cause the issue with file streaming from core to web tier. The will fix it and release bug fix version as soon as possible. Thank you for reporting the problem! You can track the status here https://youtrack.cuba-platform.com/issue/PL-9648
Single war deployment is not affected by this problem, so you can use it as a workaround.
krivopustov
(Konstantin Krivopustov)
September 7, 2017, 7:32am
#9
No need. We have found the cause, see below.
parmelim
(Pedro Armelim)
September 7, 2017, 4:29pm
#10
Hello
I can confirm that the problem is solved in 6.6.3.
Thank you Yuriy, Konstantin
Best Regards
1 Like