IcedTeaWeb + Tomcat Cause "Unexpected End of ZLIB Input Stream" While Caching

[orhanmustafa]

There are a few issues (566) of IcedTeaWeb failing to cache the JNLP properly. Specifically it being empty due to "Unexpected end of ZLIB input stream" error.

In my case I'm pretty sure it's the combination of AdoptOpenJDK IcedTeaWeb and Tomcat (7 and 8), since

• I can run other JNLPs (Oracle's DynamicTree example) with AdoptOpenJDK IcedTeaWeb;
• that same Orable example application fails when I upload it to my server (JNLP and JAR);
• I can run my application on my Tomcat with other Webstarts (RedHat, Oracle, OpenWebStart)

Here are some details: webstart.log application6.jnlp.txt server.xml.txt (standard Tomcat installation + https enabled)

curl -H "Accept-Encoding: gzip" -I https://example.com:8443/testsystem/application6.jnlp

HTTP/1.1 200
Vary: accept-encoding
Accept-Ranges: bytes
ETag: W/"1643-1632753540961"
Last-Modified: Mon, 27 Sep 2021 14:39:00 GMT
Content-Encoding: gzip
Content-Type: application/x-java-jnlp-file
Transfer-Encoding: chunked

I can only change the server - Tomcat, JNLPs, JARs. I can't touch the client Java or Webstart installation. Our clients have the latest AdoptOpenJDK and IcedTeaWeb deployed by their administrator.

Any ideas or workarounds, other then simply "using OpenWebStart" which is not applicable for me? What other Tomcat configuration could cause this behaviour?

Thanks!

[janakmulani]

Can you please try with compression=off in server.xml? Just a guess.

[orhanmustafa]

Can you please try with compression=off in server.xml? Just a guess.

Thank you for your reply, @janakmulani. The standard setting was no compression (default is "off"). same behaviour there. Turning it on was my attempt to fix the error on client, which always seems to try to extract a gzip, no matter if the server sends with or without compression.

[sclassen]

The error is known and is not effecting ITW 2.x Unfortunately there is currently no ETA for ITW 2.x

Can you try and disable the ZLIB compression on the server

[orhanmustafa]

Thanks @sclassen. I tried setting compression="off" (default) explicitly - that didn't help either. I was having the issue with the default off setting in the first place.

I wonder how come I can launch the Oracle Demo with IcedTeaWeb? How does the Oracle Server go around this issue? Or is there something special about the Orcale jar files?

[anlsmsk]

excuse me, any solution on that? Still having that issue with 1.8.X versions of IcedTeaweb.

[sclassen]

check out https://github.com/karakun/OpenWebStart

[anlsmsk]

thank you sclassen but looking for another workaround except it ?

[lherschi]

This Issue should be closed. The fix has been merged for over a year.