小程序无法加载
在测试我们的用户验收测试设置时,我们收到一些报告,表明我们的 Web 应用程序中的 Java 小程序偶尔会无法加载。报错的envt是WinXP/IE6,java控制台没有发现错误。
显然我们想避免它。我们应该在这里检查什么样的事情?在我们的本地服务器上,一切似乎都很好。向现场人员发送问题需要一些周转时间,因此我希望尽可能多地涵盖可能的原因。
更多信息: 我们有多个小程序,如果它们加载失败,则所有小程序都加载失败。 applet jar 文件的大小从 2MB 到 8MB 不等。有人告诉我,如果小程序尚未缓存,则似乎更有可能发生这种情况,即如果他们能够在给定机器上加载小程序一次,那么在该机器上进一步运行就会顺利进行。我想知道下载小程序时是否存在某种网络传输错误,但我不知道如何验证。
欢迎任何建议!
While testing our setup for user acceptance testing, we got some reports that java applets in our web application would occasionally fail to load. The envt where it was reported was WinXP/IE6, and there were no errors found in the java console.
Obviously we'd like to avoid it. What sort of things should we be checking for here? On our local servers, everything seems fine. There's some turnaround time when sending questions to the on-site guy, so I'd look to cover as many possible causes as possible.
Some more info:
We have multiple applets, in the instance that they fail loading, all of them fail loading. The applet jar files vary in size from 2MB to 8MB. I'm told it seems more likely to happen if the applet isn't cached yet, i.e. if they've been able to load the applets once on a given machine, further runs on that machine go smoothly. I'm wondering if there's some sort of network transfer error when downloading the applets, but I don't know how to verify that.
Any advise is welcome!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
故障机器上的 JRE 是否可能存在版本依赖性/不匹配?我遇到过一些需要 Java 6 的代码会导致没有 Java 6 的浏览器(Mac/Safari)崩溃的情况。
Is it possible that there are version dependencies/mismatches with the JRE on the failing machines? I've had some situations with code that required Java 6 crashing browsers (Mac/Safari) that didn't have it.
我在企业环境中使用小程序的经验通常会导致出现问题的三种路径之一。
客户端上的 JRE 版本不正确或冲突
客户端上的 JRE 损坏。
损坏的 IE 缓存
我发现卸载单个 JRE 通常是不够的,通常需要卸载计算机上的所有 JRE,然后仅重新安装您需要的 JRE。
另一个技巧是重置他们的 NT 配置文件。这对于纠正 IE 缓存问题也有奇效。我经常这样做,我已经记录了该过程。我通常在 JRE 卸载重新安装不起作用时执行此操作。
My experience with applets in an enterprise environment usually leads down 1 of 3 paths in regards to problems.
Incorrect or conflicting JRE versions on the client
Corrupt JRE on the client.
Corrupt IE Cache
I have found uninstalling a single JRE is usually not enough, Its often required to uninstall all JRE's on the machine and reinstall only the ones you need.
Another trick is to reset their NT profile. This does wonders to correct IE cache issues as well. Done this so often I have documented the procedure. I generally perform this when a JRE uninstall reinstall doesnt work.