从 Sun JVM 过渡到 JRockit 时需要注意的事项？
我们正在考虑将大型产品从依赖 Sun 的 JVM 过渡到 JRockit。 我还没有天真地相信这将是一个平稳的过渡（尽管我很愿意错）。
回归测试应该注意哪些问题或重点关注哪些问题？
We are thinking of transitioning a large product from relying on Sun's JVM to JRockit.
I'm not naive enough to believe that this is going to be a smooth transition (though I'd love to be wrong).
What issues should we watch out for or focus our regression testing on?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
嗯，当然有单元测试，对吧？ :-)
我使用 JRockit 只是为了“好玩”，从来没有遇到过问题。据我所知，它被用在许多各种各样的应用程序中，所以它应该可以工作。看来也通过了JCK（Sun的兼容性测试），应该是顺利的。
我认为要打破的领域是：
文件系统，线程等...都是与底层操作系统集成的虚拟机部分。如果他们使用 Sun 代码，那么出现问题的可能性就会减少。
我敢打赌，过渡确实会顺利进行。
Well, of course you have unit tests right? :-)
I have used JRockit somewhat just for "fun" and have never had issues. From what I can see it is used in a number of apps of a wide variety so it should probably just work. It seems that it has also passed the JCK (the compatibility tests from Sun), so it should be smooth.
Areas that I would think of for breaking would be:
The file system, threading, etc... are all the parts of the VM that integrate with the underlying OS. If they use the Sun code then less chance of issues.
I would bet that the transition does go smoothly.
正如我常说的：只有一种方法可以找到答案：去做！
转换应该需要大约... 30 分钟（您只需安装 JRockit 并在某处更改路径，对吧？）
您应该没事。
我过去在使用 JDBC 时遇到过非常奇怪的问题（因为有问题的代码位于
PreparedStatement引用中，众所周知，它只是一个接口。底层驱动程序完全相同。）我'关于insert into语句，到处都有这种奇怪的错误消息。老实说，这里还有另一个变量，我正在从 Java 1.2.2 迁移到 Java(JRockit) 1.4，但我认为我不应该遇到所有这些问题。
但同样，它应该足够快才能找出答案。就我而言，我发现我在<<中遇到了这些问题5 分钟，因为这只是一个实验（我参加了 BEA 开发者日，当时他们谈论了 JRockit 的出色功能），我就放弃了它。
As I always say: There is only one way to find out: do it!
The transition should take about what... 30 minutes ( you just install JRockit and change the path somewhere right? )
You should be ok.
I had problems in the past with JDBC which were extremely strange ( because the problematic code was in the
PreparedStatementreference that as we all know is just an interface. The underlaying driver was exactly the same.) I've got this strange error messages all over the place about theinsert intostatement.To be honest there was another variable here, I was migrating from Java 1.2.2 to Java(JRockit) 1.4 and yet, I think I shouldn't have had all those problems.
But again, it should be fast enough to find out. In my case I saw I had these problems in < 5 minutes and since that was just an experiment ( I attended to this BEA developers day when they talked about the great features JRockit had ) I just dismissed it.