签名applet的Java 8u31插件的原因加载慢得多 [英] java 8u31 plugin causes signed applets to load much slower
问题描述
我已经注意到，签名的Applet是装载了最新的插件（包含在Java 8u31和7u75）慢得多。我已经调试的情况相当多，我发现，这个问题直接关系到在JNLP文件中引用的jar文件的大小。的问题是，每个小程序启动时，存在需要时间的高速缓存jar文件的一些重新索引。
i have noticed that signed applets are loaded much slower with the latest plugin (included in java 8u31 and 7u75). I have debugged the situation quite a lot and i found out that the problem is directly related to the size of the jar files that are referenced in the jnlp file. The problem is that each time the applet starts, there is some 're-indexing' of the cached jar files that takes time.
要重现该问题我这样做：
我创建了一个小程序最小和我用于部署它的JNLP文件，我相当的规模（例如30MB）中增加了几个不相关的.jar文件（甚至都没有提及，因此类加载器不会加载它们）。当然，我使用的版本在JNLP和捕获所有的HTTP流量，以确保延误是因为交通（或者重新下载或证书吊销检查等）没有。我运行启用，然后通过XML跟踪日志文件去了，发现了跟踪的小应用程序，其中的拖延来了：他们总是从JarSigningVerifier ....
To reproduce the issue i did this: I created a minimal applet and in the jnlp file i used to deploy it, I added several irrelevant .jar files (that are not even referenced, so the classloader does not load them) of considerable size (e.g. 30MB). Of course i am using versioning in the jnlp and capture all http traffic to make sure that the delays are not because of traffic (either re-downloading or certificate revocation checks, etc). I run the applet with the trace enabled and then went through the xml trace log file and found out where the delays come: they are always from the JarSigningVerifier ....
有其他人看到类似的东西？
Has anyone else seen something like that?
这是很容易看到并重现此问题，我不知道是否有什么我可以俯瞰。在小程序已经工作了多年的广泛应用，我完全失去了什么都可以发生。我可以验证恢复到插件的previous版本（和之前所有其他版本）按预期工作。
It is very easy to see and reproduce this behavior and i wonder if there is something i am overlooking. Having worked on applets for the past years extensively, i am totally lost at what can be happening. I can verify that reverting to the previous version of the plugin (and every other version before) works as expected.
我已经提交了一个与Oracle的bug报告，但我还没有听说过静止。任何信息或想法会有所帮助，
TIA
I have submitted a bug report with oracle, but i haven't heard back still. Any info or idea will help, TIA
推荐答案
您是否能解决这个问题？你有过甲骨文的反应？
Have you been able to solve this issue? Have you had a reaction from Oracle?
更新开始
-
我用尽了一切我能想到的和没有设法解决
问题，所以我posted我自己在这个问题上问题。
类似的错误报告可以在这里被发现和被回迁在
这是我测试过的Java至少8u51。然而，他们又设法增加
启动时间为我们的应用程序。
A similar bug report can be found here and is backported to at least Java 8u51 which I tested. Yet again they managed to increase startup time for our application.
END更新
我们正在使用Java Web Start与罐子一个基于Eclipse RCP的应用程序都签名。
启动时间是在IDE中8S，Java版本似乎并不在这里无所谓。随着网络展开故事是不同的。它变（多）用糟糕每个Java更新：
We are using Java Web Start for an Eclipse RCP-based application with jars that are all signed. Startup time is 8s within the IDE, Java version doesn't seem to matter here. With web start the story is different. It becomes (much) worse with every Java update:
- 7U？ （小于60）：2秒+（10秒）
- 7u60：+ 5S（13S）
- 7u75：+ 15S（23S）
- 8u31：+ 12S（20S）
- 8u40：+ -21（-29）
- 8u51：+ 23S（31S）
这篇关于签名applet的Java 8u31插件的原因加载慢得多的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
