| FileDialog issue with http2 enabled [message #1831157] |
Wed, 12 August 2020 10:33  |
Eclipse User |
|
|
|
Hello,
Our RAP application is package as a regular WAR with servlet bridge.
We tried to enable http2 with tomcat9 (latest 9.0.37) by updating https connector on our tomcat instance.
<Connector port="8443" protocol="org.apache.coyote.http11.Http11Nio2Protocol" maxThreads="150" connectionTimeout="20000"
SSLEnabled="true" scheme="https" secure="true" clientAuth="false" sslEnabledProtocols="TLSv1, TLSv1.1, TLSv1.2"
keystoreFile="/home/arnaud-mergey/progs/apache-tomcat-9.0.37/conf/.keystore" keystorePass="changeit">
<UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol"/>
</Connector>
Then it was not possible anymore to upload file using FileDialog depending of network latency (we hit the tomcat overhead protection, it is very similar to what is described in this thread https://stackoverflow.com/questions/61413934/http2-err-connection-closed-too-much-overhead)
I was able to reproduce with latest rap demo packaged as war (attached here if needed) and Firefox (activating 'Good 3G' throttling) upploading a 15 meg image
I have attached catalina.out with http2 logs (the failure occurs around line 3412)
It is possible to make things work by disabling tomcat overheadDataThreshold but seems to be more a workaround than a fix.
I do not know enough client side of RAP file dialog to have a clear understanding of the issue (and if there is any on RAP side), what do you think ?
Best,
Arnaud
Attachment: rap-demo.war
(Size: 23.67MB, Downloaded 98 times)-
Attachment: catalina.out
(Size: 872.33KB, Downloaded 101 times)
[Updated on: Wed, 12 August 2020 10:43] by Moderator |
|
|
|
| Re: FileDialog issue with http2 enabled [message #1832198 is a reply to message #1832187] |
Fri, 11 September 2020 06:39  |
| Eclipse User |
|
|
|
I can try to reproduce with Jetty but, I do not know how to enable http/2 running from the IDE., need some time to find how
The issue is probably not backend-side, but frontend-side.
I also suspect some issues also related to session push has sometimes browsing a RAP application based on workbench, some connections are "killed" so there is the RAP error dialog "Network Error the server seems unavailable"
This can be workaround by completely disable overhead protection in tomcat
Issues are more frequent when the browser is far from the app server (cloud environment for example), when browser and server are on the same network (and fast), no issues
What I experienced is very similar to what is described here
https://stackoverflow.com/questions/61413934/http2-err-connection-closed-too-much-overhead
Its the answer of the tomcat guy who pointed me to overhead protection configuration to workaround it in the first place
[Updated on: Fri, 11 September 2020 06:40] by Moderator |
|
|
Powered by
FUDForum. Page generated in 0.03063 seconds
Home