VMThread.java

本文详细解析了VMThread类的结构和关键方法,包括堆栈大小配置、线程启动、中断处理等核心功能,并讨论了不支持的线程方法的替代方案。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

下载 VMThread.java
001 /**
002  * Copyright (C) 2007 The Android Open Source Project
003  *
004  * Licensed under the Apache License, Version 2.0 (the "License");
005  * you may not use this file except in compliance with the License.
006  * You may obtain a copy of the License at
007  *
008  *      http://www.apache.org/licenses/LICENSE-2.0
009  *
010  * Unless required by applicable law or agreed to in writing, software
011  * distributed under the License is distributed on an "AS IS" BASIS,
012  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
013  * See the License for the specific language governing permissions and
014  * limitations under the License.
015  */
016  
017 package java.lang;
018  
019 import java.util.logging.Logger;
020 import java.util.logging.Level;
021  
022 class VMThread
023 {
024     Thread thread;
025     int vmData;
026  
027     VMThread(Thread t) {
028         thread = t;
029     }
030  
031     native static void create(Thread t, long stacksize);
032  
033     static native Thread currentThread();
034     static native boolean interrupted();
035     static native void sleep (long msec, int nsec) throws InterruptedException;
036     static native void yield();
037  
038     native void interrupt();
039  
040     native boolean isInterrupted();
041  
042     /***
043      *  Starts the VMThread (and thus the Java Thread) with the given
044      *  stacksize.
045      *
046      * @param stacksize
047      *                 The desired stacksize.
048      */
049     void start(long stacksize) {
050         VMThread.create(thread, stacksize);
051     }
052  
053     private static final String UNSUPPORTED_THREAD_METHOD
054             "Deprecated Thread methods are not supported.";
055  
056     /***
057      * Suspends the Thread.
058      */
059     @SuppressWarnings("ThrowableInstanceNeverThrown")
060     void suspend() {
061         Logger.global.log(Level.SEVERE, UNSUPPORTED_THREAD_METHOD,
062                 new UnsupportedOperationException());
063     }
064  
065     /***
066      * Resumes the Thread, assuming it is suspended.
067      */
068     @SuppressWarnings("ThrowableInstanceNeverThrown")
069     void resume() {
070         Logger.global.log(Level.SEVERE, UNSUPPORTED_THREAD_METHOD,
071                 new UnsupportedOperationException());
072     }
073  
074     /***
075      * Queries whether this Thread holds a monitor lock on the
076      * given object.
077      */
078     native boolean holdsLock(Object object);
079  
080     /***
081      * Stops the Thread, passing it a Throwable (which might be ThreadDeath).
082      */
083     @SuppressWarnings("ThrowableInstanceNeverThrown")
084     void stop(Throwable throwable) {
085         Logger.global.log(Level.SEVERE, UNSUPPORTED_THREAD_METHOD,
086                 new UnsupportedOperationException());
087     }
088  
089     native void setPriority(int newPriority);
090     native int getStatus();
091  
092     /***
093      * Holds a mapping from native Thread statii to Java one. Required for
094      * translating back the result of getStatus().
095      */
096     static final Thread.State[] STATE_MAP = new Thread.State[] {
097         Thread.State.TERMINATED,     // ZOMBIE
098         Thread.State.RUNNABLE,       // RUNNING
099         Thread.State.TIMED_WAITING,  // TIMED_WAIT
100         Thread.State.BLOCKED,        // MONITOR
101         Thread.State.WAITING,        // WAIT
102         Thread.State.NEW,            // INITIALIZING
103         Thread.State.NEW,            // STARTING
104         Thread.State.RUNNABLE,       // NATIVE
105         Thread.State.WAITING         // VMWAIT
106     };
107  
108     /***
109      * Tell the VM that the thread's name has changed.  This is useful for
110      * DDMS, which would otherwise be oblivious to Thread.setName calls.
111      */
112     native void nameChanged(String newName);
113 }
java: java.lang.OutOfMemoryError: Java heap space java.lang.RuntimeException: java.lang.OutOfMemoryError: Java heap space at com.sun.tools.javac.main.Main.compile(Main.java:559) at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138) at org.jetbrains.jps.javac.JavacMain.compile(JavacMain.java:239) at org.jetbrains.jps.javac.ExternalJavacProcess.compile(ExternalJavacProcess.java:189) at org.jetbrains.jps.javac.ExternalJavacProcess.access$400(ExternalJavacProcess.java:28) at org.jetbrains.jps.javac.ExternalJavacProcess$CompilationRequestsHandler$1.run(ExternalJavacProcess.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.OutOfMemoryError: Java heap space at java.io.BufferedInputStream.<init>(BufferedInputStream.java:203) at java.io.BufferedInputStream.<init>(BufferedInputStream.java:183) at org.jetbrains.jps.javac.ZipFileObject.openInputStream(ZipFileObject.java:48) at com.sun.tools.javac.api.ClientCodeWrapper$WrappedFileObject.openInputStream(ClientCodeWrapper.java:426) at com.sun.tools.javac.jvm.ClassReader.fillIn(ClassReader.java:2510) at com.sun.tools.javac.jvm.ClassReader.complete(ClassReader.java:2442) at com.sun.tools.javac.jvm.ClassReader.access$000(ClassReader.java:76) at com.sun.tools.javac.jvm.ClassReader$1.complete(ClassReader.java:240) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:574) at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:1037) at com.sun.tools.javac.code.Symbol$ClassSymbol.members(Symbol.java:978) at com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.visitEnumAttributeProxy(ClassReader.java:1854) at com.sun.tools.javac.jvm.ClassReader$EnumAttributeProxy.accept(ClassReader.java:1676) at com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.deproxy(ClassReader.java:1814) at com.sun.tools.javac.jvm.ClassReader$AnnotationDefaultCompleter.run(ClassReader.java:1918) at com.sun.tools.javac.comp.Annotate.flush(Annotate.java:143) at com.sun.tools.javac.comp.Annotate.enterDone(Annotate.java:129) at com.sun.tools.javac.comp.Enter.complete(Enter.java:512) at com.sun.tools.javac.comp.Enter.main(Enter.java:471) at com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:982) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.enterTrees(JavacProcessingEnvironment.java:1015) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.<init>(JavacProcessingEnvironment.java:902) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.next(JavacProcessingEnvironment.java:921) at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1187) at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856) at com.sun.tools.javac.main.Main.compile(Main.java:523) at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138) at org.jetbrains.jps.javac.JavacMain.compile(JavacMain.java:239) at org.jetbrains.jps.javac.ExternalJavacProcess.compile(ExternalJavacProcess.java:189) at org.jetbrains.jps.javac.ExternalJavacProcess.access$400(ExternalJavacProcess.java:28)
最新发布
05-20
### Java编译过程中出现 `java.lang.OutOfMemoryError: Java heap space` 的解决方案 #### 背景分析 在Java开发中,`java.lang.OutOfMemoryError: Java heap space` 错误表明应用程序尝试使用的内存超出了JVM堆的最大限制。这种错误可能由多种原因引起,包括但不限于内存泄漏、大对象的频繁创建以及不合理的JVM参数设置。 此问题不仅限于运行时环境,在编译阶段也可能发生类似的错误。尤其是在处理大型项目或复杂依赖关系时,编译器本身可能会消耗大量内存,从而触发该异常[^1]。 --- #### JVM堆内存调整方法 为了有效解决这一问题,可以考虑通过增加JVM堆内存来缓解压力: 1. **修改IDE配置** 如果您正在使用IntelliJ IDEA作为集成开发环境,则可以通过以下方式调整其JVM选项: - 打开IDEA安装目录下的`bin/idea64.vmoptions`文件(Windows系统下路径为`<IDEA_HOME>/bin/idea64.exe.vmoptions`),找到并编辑如下字段: ```plaintext -Xms512m -Xmx2048m -XX:MaxPermSize=512m ``` 将`-Xmx`值增大到适合您的硬件条件的范围,例如`4g`代表4GB。 修改完成后保存文件,并重启IDEA以使更改生效[^2]。 2. **命令行编译时指定JVM参数** 当采用命令行方式进行编译时,也可以手动传递额外的JVM参数给javac工具。例如: ```bash javac -J-Xms512m -J-Xmx4g YourSourceFile.java ``` 这里的`-J`前缀允许我们将标准JVM选项传入至编译过程之中[^3]。 3. **Tomcat服务器场景优化** 对于基于Tomcat的应用部署情况,同样存在因内存不足而引发此类错误的可能性。此时需针对Tomcat服务端做出相应改动: 编辑位于`$TOMCAT_HOME/bin/catalina.bat`(Windows) 或 `$TOMCAT_HOME/bin/catalina.sh`(Linux/MacOS),追加下列内容至JAVA_OPTS变量定义部分: ```sh JAVA_OPTS="$JAVA_OPTS -Xms512m -Xmx2048m" ``` 此外还可以启用GC日志记录功能以便后续排查潜在性能瓶颈: ```sh JAVA_OPTS="$JAVA_OPTS -verbose:gc -Xloggc:/path/to/gc.log -XX:+PrintGCDetails" ``` 完成以上步骤之后重新启动Tomcat即可验证效果[^4]。 --- #### 额外建议 除了单纯扩大可用堆空间之外,还应关注以下几个方面来进一步改善整体表现: - **代码层面改进**: 检查是否存在不必要的大规模数组初始化或其他可能导致瞬态高内存需求的操作;适当拆分任务降低单次执行所需资源量; - **垃圾回收机制调优**: 不同版本JDK提供了多样化的GC算法实现形式(如Parallel GC, CMS GC,G1 GC,ZGC等),依据实际业务特点选取最合适的策略有助于提升效率减少停顿时间; - **监控与诊断工具运用**: 利用VisualVM,JConsole或者第三方APM(Application Performance Management)产品持续跟踪线上实例状态变化趋势及时发现隐患所在. --- ### 示例代码展示 以下是利用VisualVM连接远程主机上的Tomcat进程的一个简单例子: ```bash jvisualvm --openfile /usr/local/tomcat/logs/jstatd.pid ``` 上述指令假设目标机器已预先开启监听端口并通过防火墙规则放通对应流量方向;具体操作细节可参照官方文档说明链接地址[^4]. ---
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值