为什么 Mac OS X 上的 VPN 连接会导致 Eclipse 在“编辑启动配置”期间锁定？手术？
我一直在家里通过 VPN 在 Mac OS X 上使用 Eclipse，为我的雇主在本地工作区中开发 GWT 和 Perl 代码。最近，每当我尝试编辑调试（或运行）启动配置时，就会出现可重复且严重的锁定。我得到了旋转的死亡沙滩球 (SBOD)，如果我等待足够长的时间（10-15 分钟），它最终会停止，我至少可以关闭对话框。
我尝试了很多方法，直到一位同事建议尝试关闭 VPN。令我惊讶（也有点高兴）的是，它在上述场景中开始表现正常。我已经以这种方式使用 Eclipse 大约一年了，没有出现任何问题，所以我很自然地绞尽脑汁试图思考最近对 VPN 和/或我的分割隧道脚本（委婉地称为“多主”）的更改可以解释这一点异常行为。无论有或没有分割隧道，都会发生这种锁定。
我还应该指出，启动 eclipse 时总是会出现“正在初始化 Java 工具”进度状态，并且需要大约一分钟才能完成 VPN 连接。正常（<2 秒）无。
因此，我开始学习如何使用wireshark，并且可能还会研究使用packetlogger，以试图找到有关这个奇怪问题的更多信息。
任何人都知道可能导致此问题的原因是什么？
I have been using Eclipse on Mac OS X from home over a VPN to develop GWT and perl code in a local workspace for my employer. Recently a repeatable and severe lockup began occurring whenever I tried to edit Debug (or Run) launch configurations. I got the spinning beachball of death (SBOD) and, if I waited long enough (10-15 minutes) it would eventually stop and I could at least close the dialog.
I tried numerous things until a coworker suggested trying it with VPN turned off. To my surprise (and somewhat delight) it began behaving normally in the above scenario. I have been using Eclipse in this manner for about a year with no problems so naturally I am racking my brain trying to think of recent changes to VPN and/or to my split tunnel script (euphemistically called 'multihome') that could account for this abnormal behavior. This lockup occurs with or without the split tunnel.
I should also point out that the "initializing Java tooling" progress status ALWAYS occurs when starting eclipse and takes about a minute to complete with VPN connection. Normal (<2 seconds) without.
So, I'm starting to learn how to use wireshark and possibly will look into using packetlogger as well in an attempt to find out more about this strange issue.
Anyone have a clue as to what might be causing this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这是一个很难回答的问题。简短的回答是“我不知道”。
然而，我确实发现，由于最近更新了 JVM（作为 Mac OS X 更新的一部分），Eclipse IDE 失去了查找 JRE 的 src.jar 文件的能力。因此，Eclipse 似乎在代码中的各个位置搜索了该文件，并且在未找到时尝试通过网络查找它。当VPN打开时，也许这会加剧问题。
通过修复 Eclipse 的已安装 JRE 配置解决了这个问题（请参阅 OSX 10.7 Lion 上的 JDK）。
This is a hard one to answer. Short answer is "I don't know".
However, I did find out that, due to the recently updated JVM, done as part of the Mac OS X update, Eclipse IDE lost its ability to find the src.jar file for the JRE. As a result, it appears that Eclipse, in various places in the code, searched for this file and when not found attempted to find it via the network. When VPN was turned on, perhaps this exacerbated the problem.
This was solved by fixing the Installed JRE configuration of Eclipse (see JDK on OSX 10.7 Lion).