java虚拟机 jvm 的启动_java虚拟机jvm启动后java代码层面发生了什么?

最新推荐文章于 2022-04-20 07:16:03 发布
最新推荐文章于 2022-04-20 07:16:03 发布
阅读量170 收藏
点赞数
文章标签： java虚拟机 jvm 的启动
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_39813009/article/details/114356824
版权

"RMI TCP Connection(2)-192.168.191.1" #18 daemon prio=5 os_prio=0 tid=0x000000001b409800 nid=0x80a4 runnable [0x000000001c93d000]

java.lang.Thread.State: RUNNABLE

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)

at java.net.SocketInputStream.read(SocketInputStream.java:171)

at java.net.SocketInputStream.read(SocketInputStream.java:141)

at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)

at java.io.BufferedInputStream.read(BufferedInputStream.java:265)

- locked <0x00000000d7520cb0> (a java.io.BufferedInputStream)

at java.io.FilterInputStream.read(FilterInputStream.java:83)

at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:555)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$Lambda$3/1223273742.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)

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)

Locked ownable synchronizers:

- <0x00000000d6c99530> (a java.util.concurrent.ThreadPoolExecutor$Worker)

"JMX server connection timeout 17" #17 daemon prio=5 os_prio=0 tid=0x000000001ae9e000 nid=0x8088 in Object.wait() [0x000000001c63f000]

java.lang.Thread.State: TIMED_WAITING (on object monitor)

at java.lang.Object.wait(Native Method)

- waiting on <0x00000000d715f378> (a [I)

at com.sun.jmx.remote.internal.ServerCommunicatorAdmin$Timeout.run(ServerCommunicatorAdmin.java:168)

- locked <0x00000000d715f378> (a [I)

at java.lang.Thread.run(Thread.java:748)

Locked ownable synchronizers:

- None

"RMI Scheduler(0)" #16 daemon prio=5 os_prio=0 tid=0x000000001b1c6800 nid=0x8084 waiting on condition [0x000000001c53e000]

java.lang.Thread.State: TIMED_WAITING (parking)

at sun.misc.Unsafe.park(Native Method)

- parking to wait for <0x00000000d69fbee0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)

at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)

at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)

at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)

at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)

at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

Locked ownable synchronizers:

- None

"RMI TCP Connection(1)-192.168.191.1" #15 daemon prio=5 os_prio=0 tid=0x000000001ae1a800 nid=0x8080 runnable [0x000000001c43d000]

java.lang.Thread.State: RUNNABLE

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)

at java.net.SocketInputStream.read(SocketInputStream.java:171)

at java.net.SocketInputStream.read(SocketInputStream.java:141)

at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)

at java.io.BufferedInputStream.read(BufferedInputStream.java:265)

- locked <0x00000000d6ddc2e0> (a java.io.BufferedInputStream)

at java.io.FilterInputStream.read(FilterInputStream.java:83)

at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:555)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$3/1223273742.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)

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)

Locked ownable synchronizers:

- <0x00000000d6c93ac0> (a java.util.concurrent.ThreadPoolExecutor$Worker)

"RMI TCP Accept-0" #14 daemon prio=5 os_prio=0 tid=0x000000001a833800 nid=0x8074 runnable [0x000000001c23e000]

java.lang.Thread.State: RUNNABLE

at java.net.DualStackPlainSocketImpl.accept0(Native Method)

at java.net.DualStackPlainSocketImpl.socketAccept(DualStackPlainSocketImpl.java:131)

at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409)

at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:199)

- locked <0x00000000d6be9bb0> (a java.net.SocksSocketImpl)

at java.net.ServerSocket.implAccept(ServerSocket.java:545)

at java.net.ServerSocket.accept(ServerSocket.java:513)

at sun.management.jmxremote.LocalRMIServerSocketFactory$1.accept(LocalRMIServerSocketFactory.java:52)

at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:405)

at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:377)

at java.lang.Thread.run(Thread.java:748)

Locked ownable synchronizers:

- None

"Service Thread" #12 daemon prio=9 os_prio=0 tid=0x000000001a653800 nid=0x3be8 runnable [0x0000000000000000]

java.lang.Thread.State: RUNNABLE

Locked ownable synchronizers:

- None

"C1 CompilerThread2" #11 daemon prio=9 os_prio=2 tid=0x000000001a63f000 nid=0x70b8 waiting on condition [0x0000000000000000]

java.lang.Thread.State: RUNNABLE

Locked ownable synchronizers:

- None

"C2 CompilerThread1" #10 daemon prio=9 os_prio=2 tid=0x000000001a5ed800 nid=0x7898 waiting on condition [0x0000000000000000]

java.lang.Thread.State: RUNNABLE

Locked ownable synchronizers:

- None

"C2 CompilerThread0" #9 daemon prio=9 os_prio=2 tid=0x000000001a5ec800 nid=0x79a4 waiting on condition [0x0000000000000000]

java.lang.Thread.State: RUNNABLE

Locked ownable synchronizers:

- None

"JDWP Command Reader" #8 daemon prio=10 os_prio=0 tid=0x0000000018458800 nid=0x7520 runnable [0x0000000000000000]

java.lang.Thread.State: RUNNABLE

Locked ownable synchronizers:

- None

"JDWP Event Helper Thread" #7 daemon prio=10 os_prio=0 tid=0x0000000018455000 nid=0x7c44 runnable [0x0000000000000000]

java.lang.Thread.State: RUNNABLE

Locked ownable synchronizers:

- None

"JDWP Transport Listener: dt_socket" #6 daemon prio=10 os_prio=0 tid=0x0000000018449000 nid=0x7a50 runnable [0x0000000000000000]

java.lang.Thread.State: RUNNABLE

Locked ownable synchronizers:

- None

"Attach Listener" #5 daemon prio=5 os_prio=2 tid=0x00000000197b3000 nid=0x3250 waiting on condition [0x0000000000000000]

java.lang.Thread.State: RUNNABLE

Locked ownable synchronizers:

- None

"Signal Dispatcher" #4 daemon prio=9 os_prio=2 tid=0x000000001842a800 nid=0x4c8c runnable [0x0000000000000000]

java.lang.Thread.State: RUNNABLE

Locked ownable synchronizers:

- None

"Finalizer" #3 daemon prio=8 os_prio=1 tid=0x00000000037bd800 nid=0x764c in Object.wait() [0x000000001976f000]

java.lang.Thread.State: WAITING (on object monitor)

at java.lang.Object.wait(Native Method)

- waiting on <0x00000000d5d88ed0> (a java.lang.ref.ReferenceQueue$Lock)

at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)

- locked <0x00000000d5d88ed0> (a java.lang.ref.ReferenceQueue$Lock)

at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)

at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:216)

Locked ownable synchronizers:

- None

"Reference Handler" #2 daemon prio=10 os_prio=2 tid=0x00000000037bc000 nid=0x3c8c in Object.wait() [0x000000001966e000]

java.lang.Thread.State: WAITING (on object monitor)

at java.lang.Object.wait(Native Method)

- waiting on <0x00000000d5d86bf8> (a java.lang.ref.Reference$Lock)

at java.lang.Object.wait(Object.java:502)

at java.lang.ref.Reference.tryHandlePending(Reference.java:191)

- locked <0x00000000d5d86bf8> (a java.lang.ref.Reference$Lock)

at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)

Locked ownable synchronizers:

- None

"main" #1 prio=5 os_prio=0 tid=0x00000000036c4000 nid=0x1cb0 runnable [0x00000000035bf000]

java.lang.Thread.State: RUNNABLE

at java.io.FileInputStream.readBytes(Native Method)

at java.io.FileInputStream.read(FileInputStream.java:255)

at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)

at java.io.BufferedInputStream.read(BufferedInputStream.java:265)

- locked <0x00000000d5de89a8> (a java.io.BufferedInputStream)

at com.TaskTest.main(Test.java:179)

Locked ownable synchronizers:

- None

"VM Thread" os_prio=2 tid=0x00000000183d8000 nid=0x6d38 runnable

"GC task thread#0 (ParallelGC)" os_prio=0 tid=0x00000000036e2800 nid=0x7e88 runnable

"GC task thread#1 (ParallelGC)" os_prio=0 tid=0x00000000036e4000 nid=0x35e4 runnable

"GC task thread#2 (ParallelGC)" os_prio=0 tid=0x00000000036e5800 nid=0x4ed4 runnable

"GC task thread#3 (ParallelGC)" os_prio=0 tid=0x00000000036e7000 nid=0x702c runnable

"VM Periodic Task Thread" os_prio=2 tid=0x000000001a69f000 nid=0x2af8 waiting on condition

JNI global references: 5253

weixin_39813009
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Java避免死锁的几个常见方法(有测试代码和分析过程)
liuruiaaa的博客
04-14 2195
Java避免死锁的几个常见方法(有测试代码和分析过程)
Java 多线程&使用常见命令分析线程的信息——3
爱的叹息的专栏
05-24 2605
java代码：Thread5.java 创建5个线程,每个线程创建后睡眠500秒 package com.burns.callmainmethodmainthread; public class Thread5 { public static void main(String[] args) throws InterruptedException { for (int i = 0; i < 5; i++) { new Thread() {
Java线程＜二＞ _ Thread Dump日志分析
爱我所爱0505
01-25 3347
目录 一、查看CPU上下文切换 1.vmstat命令 2. pidstat命令 二、JVM的jstack命令 1. JVM的jstack命令 2. 堆栈信息的线程状态 三、 Thread Dump日志分析 1. 导出堆栈信息 2.堆栈信息实例 实例一：BLOCKED (on object monitor) 实例二：TIMED_WAITING (sleeping) 实例三：TIMED_WAITING (on object monito...
记一次线上故障的排查过程
weixin_33872566的博客
08-08 611
2019独角兽企业重金招聘Python工程师标准>>> ...
Java多线程死锁例子
Davis
03-04 534
目录一、产生死锁的原因二、如何避免死锁 一、产生死锁的原因 发生死锁的情况： 多个线程需要同时占用多个共享资源而发生需要互相死循环等待的情况，就是，两个线程互相等待着对象释放锁，一直这样僵持下去，所以导致了死锁的产生。 产生死锁代码： package com.javaagent.thread; public class DieThread implements Runnable { p...
Java多线程.线程检测
记录 分享 成就
04-20 1427
visualVM VisualVM是JDK自带的一款全能型性能监控和故障分析工具，包括对CPU使用、JVM堆内存消耗、线程、类加载的实时监控，内存dump文件分析，垃圾回收运行情况的可视化分析等，对故障排查和性能调优很有帮助。在windows中安装JDK后，VisualVM位于%JAVA_HOME%/bin/下，直接执行jvisualvm.exe即可，也可以配置远程监控JVM，VisualVM连接远程服务器有两种方式：JMX和jstatd，两种方式都不能完美支持所有功能，例如JMX不支持VisualGC，
【Tomcat】Tomcat运行报错RMI TCP Accept-0排查处理
cnskylee的博客
03-22 6324
报错信息： 22-Mar-2022 14:27:16.513 WARNING [RMI TCP Accept-0] sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,localport=45995] throws java.io.IOException: The server sockets
[java] jstack 查看死锁问题
a84480766的博客
01-04 417
package com.xwolf.java.thread.ch2; /** * Created by Administrator on 2016/1/4 0004. */ public class DeadLock { private static String a ="A"; private static String b ="B"; ...
Java多线程死锁案例
墨笙弘一
06-28 3090
产生死锁的原因 就是，两个线程互相等待着对象释放锁，一直这样僵持下去，所以导致了死锁的产生，下面这个代码就会产生一个死锁： package com.example.demo.thread; public class DeadLockDemo { private static String A = "A"; private static String B = "B"; p...
Java线程状态分析/线程状态转换图
热门推荐
shi2huang的博客
05-12 1万+
注：以下代码讲解基于JDK1.8.0_144一、线程状态分类 线程一共有六种状态，分别为New、RUNNABLE、BLOCKED、WAITING、TIMED_WAITINGTERMINATED，同一时刻只有一种状态，通过线程的getState方法可以获取线程的状态。二、线程状态讲解2.1 NEW      /**         * Thread state for a thread which ...
jps,jstack检测java死锁
xiaomin1991222的专栏
03-10 777
import java.util.concurrent.CountDownLatch; import java.util.concurrent.ExecutorService; import java.util.concurrent.Executors; /** * Hello world! */ public class App { pub
java 获取线程状态_Java语言定义的线程状态分析
weixin_28725553的博客
02-12 545
说到线程，一定要谈到线程状态，不同的状态说明线程正处于不同的工作机制下，不同的工作机制下某些动作可能对线程产生不同的影响。Java语言定义了6中状态，而同一时刻，线程有且仅有其中的一种状态。要获取Java线程的状态可以使用 java.lang.Thread类中定义的 getState()方法，获取当前线程的状态就可以使用Thread.currentThread().getState()来获取。该方...
启动 SpringBoot 时出现：java.io.IOException: The server sockets created using the LocalRMIServerSocketFact
yage124的博客
07-06 1万+
【问题描述】 新创建一个 SpringBoot 项目运行，出现一下异常： java.io.IOException: The server sockets created using the LocalRMIServerSocketFactory only accept connections from clients running on the host where the RMI remote objects have been exported. at sun.management.jmxremot
SpringBoot启动时出现：java.io.IOException: The server sockets created using the LocalRMIServerSocketFactor
weixin_45948019的博客
10-16 1万+
错误内容如下： 在使用idea时出现下面错误，idea版本为2019.3，jdk版本为11 java.io.IOException: The server sockets created using the LocalRMIServerSocketFactory only accept connections from clients running on the host where the RMI remote objects have been exported. at jdk.management
Jstack 分析哪一行代码慢 ？jvm 打印出线程栈分析
Top5软件工程硕士，先后在京东、字节从事多年Java后端开发、实时和离线大数据开发
02-27 915
面试题：后台只有一台服务器，上线后发现，只有1个接口请求很慢，其他接口的请求和反应时间很正常，该怎么分析？怎么找出是哪行代码导致的慢？ 是在线上，当然不能测试或单步调试。 答案：打印出线程栈分析。 举例： /** * @Author liuyazhou * @Date 2021/2/25 16:30 * @Version 1.0 * @Desc */ /** * 同步线程 */ class SyncThread implements Runnable { private
Java多线程开发系列-线程活性故障
昕友软件博客
03-18 428
由资源稀缺性或者程序自身的问题和缺陷导致线程一直处于非Runnable状态，或者线程虽然处于Runnable状态但是其要执行的任务却一直无法进展的故障现象。 有4种情况 死锁 锁死 饥饿 活锁 死锁 如果线程A持有锁L并且想获得锁M，线程B持有锁M并且想获得锁L，那么这两个线程将永远等待下去，这种情况就是最简单的死锁形式。在数据库系统的设计中考虑了监测死锁以及从死锁中恢复，数据库如果...
jvm之AccessController.doPrivileged
大佬请赐教
02-25 1万+
AccessController.doPrivileged在底层源码中会出现，本文对它进行一个简单介绍及如何使用的说明。 首先解释一下几个相关概念保护域 类被装入jvm，为每个类指定一个保护域，保护域定义了授予一段特定代码的所有权限，一个保护域对应一个策略policy.txt文件的一个或者多个grant子句，被装入jvm的每一个类型仅属于一个保护域。 那么一个类型如何被指派到保护域呢？ 类装载器...
java mysql 线程阻塞_java线程阻塞问题排查方法
weixin_30696571的博客
02-11 519
我开发的worker，每隔几个月线上都会阻塞一次，一直都没查出问题。今天终于了了这个心结。把解决过程总结下和大家分享。首先用jstack命令打出这个进程的全部线程堆栈。拿到线程dump文件之后，搜索自己的worker名字。"DefaultQuartzScheduler_Worker-10" prio=10 tid=0x00007f55cd54d800 nid=0x3e2e waiting for ...
进程的死锁如何产生+避免死锁方法
try to do
03-17 3527
什么是死锁 死锁是指多个进程因竞争资源而造成的一种僵局（互相等待），若无外力作用，这些进程都将无法向前推进。例如，在某一个计算机系统中只有一台打印机和一台输入 设备，进程P1正占用输入设备，同时又提出使用打印机的请求，但此时打印机正被进程P2 所占用，而P2在未释放打印机之前，又提出请求使用正被P1占用着的输入设备。这样两个进程相互无休止地等待下去，均无法继续执行，此时两个进程陷入死锁状态。 死锁...
Java虚拟机JVM面试必备知识详解
Java虚拟机（JVM）是Java程序运行的核心，它将Java源代码编译成字节码，然后在虚拟机上解释执行。面试中对JVM的理解和掌握通常是衡量开发者技能深度的重要指标。 1. **Java内存区域** - **主要组成部分及作用**： ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值