-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downloading jar files from JNLP using open web start plugin takes longer than Oracle JRE #558
Comments
can you try with Open Web Start Version 1.8.0? |
is some improvements added in 1.8.0 regarding this problem ? |
Hi Marc, We have tested on Open Web Start Version 1.8.0 as well, but still taking 3+ minutes to download jars and launch java console. Thanks |
Hi team, We have setup available and replicating issue locally, we can have web-ex and verify same. Thanks |
Hi OpenJDK Support team, Any suggestion/fix plan on this please ? Thanks |
Hi Team, Any suggestion/fix plan on this please ? Thanks |
don't have this issue, debug and use a profiler to check the bottleneck do you use a proxy |
No, we are not using proxy. |
Enabled client debug and verified the logs, the delay happening while downloading the jars. |
Hi Team, Any suggestion/fix plan on this please ? Thanks |
Hi Team,
Issue: Downloading jar files from JNLP using open web start plugin takes longer than Oracle JRE, it is taking 3 to 5 minutes in same subnetwork, network speed also good.
Adapt Open JDK Version: Java Runtime Environment version 11.0.19
Open Web Start Version : 1.7.0
Client to Server Ping test: 127 ms
Server to Client Ping Test : 127 ms
Client to Server latency Test: 100 ms
Same issue happening with IceTea-Web as well.
Adapt Open JDK Version : Java Runtime Environment version 8 update 312
IcedTea-Web Version : 1.8.8
But Oracle 1.8, it is opening in quickly 30 seconds.
Attaching open JDK debug log file for reference.
Its a high priority issue for us. Our end customer is escalating this issue and hence any quick solutions/suggestions would be highly appreciated.
We have issue replicated locally, we can have web-ex and verify.
Thanks
Channa
The text was updated successfully, but these errors were encountered: