已知的Tomcat 6.0和JDK 1.7.0_02问题？ [英] Known Tomcat 6.0 and JDK 1.7.0_02 issues?

问题描述

有没有已知的 Tomcat 6.0 和 JDK 1.7.0_02 问题？

我知道这是一个很难回答的问题，如果答案是否定的。但是我需要询问，以防万一答案是肯定的。此外，我将接受以下问题的任何解决方案作为答案。请分享您所遇到的任何问题，如有需要，我会更新此问题。

I know this is a hard question to answer, if the answer is no. But I need to ask just in case the answer is yes. Also I will accept any solutions to the issues below as answers. Please just share whatever issues you have had, and I will update this question if need be.

我从JDK 1.7.0升级到1.7.0_02（）中遇到的一些问题，我为避免Eclipse的帮助菜单崩溃，由于Java 1.7.0错误。）：

Some issues I have run into since upgrading from JDK 1.7.0 to 1.7.0_02 (which I did to avoid the Eclipse's help menus from crashing, due to a Java 1.7.0 bug.):

• Tomcat服务器需要更长的时间才能启动，我需要120秒的时间来处理它。


• 本机方法中的FATAL错误：JDWP没有传输初始化，jvmtiError = AGENT_ERROR_TRANSPORT_INIT（197）错误，第二天消失，然后重新出现第三天，除了重新加载Eclipse。


• Tomcat服务器需要更长时间才能关闭。我需要60秒的时间来处理它，从15秒的默认值。


• Eclipse本身似乎在构建工作区并验证手头的项目时停止（比喻）。 Eclipse中的所有内容似乎都需要更长时间，甚至打开未打开的文件。

• Tomcat server takes much longer to start, I need a 120 second timeout to handle it.
• FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197) error, which disappeared the next day and then reappeared the third day, with no changes other than reloading Eclipse.
• Tomcat server takes much longer to shut down. I need a 60 second timeout to handle it, from 15 second default.
• Eclipse itself appears to crawl to a halt (figuratively speaking) upon building the workspace and validating the project at hand. Everything within Eclipse appears to take longer, even opening an unopened file.

一切似乎都是可疑的。

PS JDK 1.7.0_02 也被称为 1.7.0u2 ， Java SE 7u2 ， Java SE 7 Update 2 等。

P.S. JDK 1.7.0_02 is also known as 1.7.0u2, Java SE 7u2, Java SE 7 Update 2, etc.

• JDK = Oracle ，64位，从 http://www.oracle.com/technetwork/java/javase/downloads/index.html 。正确的文件已下载并安装了 jdk-7u2-windows-x64.exe 。


• Tomcat = Tomcat 6.0 .32 ，从Eclipse单独下载


• Eclipse = 适用于Web开发人员的Eclipse Java EE IDE。 code>版本：Indigo发行， Eclipse平台，版本：3.7.0.v20110530-9gF7UHNFFt4cwE-pkZDJ7oz -mj4OSEIlu9SEv0f ， Build id：I20110613-1736 。


• 64位Windows 7机器，8GB内存，Intel Core i7-2600 CPU @ 3.4GHz（4核）


• Eclipse，Tomcat，Apache HTTP Server都在同一台（开发型）计算机上。

• JDK = Oracle, 64-bit, downloaded from http://www.oracle.com/technetwork/java/javase/downloads/index.html. Exact file downloaded and installed was jdk-7u2-windows-x64.exe.
• Tomcat = Tomcat 6.0.33, downloaded separately from Eclipse
• Eclipse = Eclipse Java EE IDE for Web Developers., Version: Indigo Release, Eclipse Platform, Version: 3.7.0.v20110530-9gF7UHNFFt4cwE-pkZDJ7oz-mj4OSEIlu9SEv0f, Build id: I20110613-1736.
• 64-bit Windows 7 machine, 8GB RAM, Intel Core i7-2600 CPU @ 3.4GHz (4 cores)
• Eclipse, Tomcat, Apache HTTP Server, are all on the same (development) computer.

编辑：上面添加了系统规格。

Added system specs above.

推荐答案

64位Java的默认选项（默认情况下，引用压缩是关闭的），它需要的内存量是32位的几乎两倍。

When running 64 bits Java with default options (references compaction is off by default), it requires almost twice the amount of memory than with 32 bits.

对于Eclipse，打开code> eclipse.ini 文件，并且双倍/增加了很多 -Xmx 选项。

For Eclipse, open the eclipse.ini file and double/increase a lot the -Xmx option.

当然，运行某些JVM时，您的物理内存可能还不够。

Of course, your physical memory may not be enough when running some JVMs.

所以我建议您测试 -XX：+ UseCompressedOops HotSpot选项，例如通过 jconsole 监视内存使用情况。您还可以阅读有关该近期选项的详细信息。该选项

So I recommend you to test the -XX:+UseCompressedOops HotSpot option with 64 bits JVM and monitor memory usage thanks to jconsole for instance. You can also read details about that recent option. That option

对于Tomcat，创建文件 bin / setenv.bat 与内容：

For Tomcat, create the file bin/setenv.bat with content:

set JAVA_OPTS="-Xmx1024M -XX:+UseCompressedOops" 

这篇关于已知的Tomcat 6.0和JDK 1.7.0_02问题？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！