JVM无法在MAC上启动并获得KILL SIGNAL(9)

2020-09-09 04:52发布

         点击此处--->   EasySAP.com群内免费提供SAP练习系统(在群公告中)

加入QQ群:457200227(SAP S4 HANA技术交流) 群内免费提供SAP练习系统(在群公告中)


在Tomcat上运行hybrisPlatform ...-> Wrapper作为控制台Java服务启动Wrapper专业版64位3.5.29版权所有(C)1999-2016 Tanuki Software,Ltd.保留所有权利。 http://wrapper.tanukisoftware.com 已获得针对hybris平台的SAP SE许可

启动JVM ...启动失败:等待JVM的信号超时。 转储JVM状态。 2019-05-05 16:28:56全线程转储Java HotSpot(TM)64位服务器VM(25.191-b12混合模式):

"服务线程"#9守护程序prio = 9 os_prio = 31 tid = 0x00007fdd6881f000 nid = 0x3d03 runnable [0x0000000000000000] java.lang.Thread.State:RUNNABLE

" C1 CompilerThread3"#8守护程序prio = 9 os_prio = 31 tid = 0x00007fdd6800a000 nid = 0x3e03等待条件[0x0000000000000000] java.lang.Thread.State:RUNNABLE

" C2 CompilerThread2"#7守护程序prio = 9 os_prio = 31 tid = 0x00007fdd68800000 nid = 0x3803等待条件[0x0000000000000000] java.lang.Thread.State:RUNNABLE

" C2 CompilerThread1"#6守护程序prio = 9 os_prio = 31 tid = 0x00007fdd68009000 nid = 0x3603等待条件[0x0000000000000000] java.lang.Thread.State:RUNNABLE

" C2 CompilerThread0"#5守护程序prio = 9 os_prio = 31 tid = 0x00007fdd67020000 nid = 0x4003等待条件[0x0000000000000000] java.lang.Thread.State:RUNNABLE

"信号分配器"#4守护程序prio = 9 os_prio = 31 tid = 0x00007fdd67824800 nid = 0x4203等待条件[0x0000000000000000] java.lang.Thread.State:RUNNABLE

" Finalizer"#3守护程序prio = 8 os_prio = 31 tid = 0x00007fdd67805800 nid = 0x4903 in Object.wait()[0x0000700010c97000] java.lang.Thread.State:在java.lang.Object上等待(在对象监视器上) .wait(本机方法)-在java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)上等待(java.lang.ref.ReferenceQueue $ Lock)-锁定(java.lang.ref.ReferenceQueue $ 锁定)在java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)在java.lang.ref.Finalizer $ FinalizerThread.run(Finalizer.java:216)

"引用处理程序"#2守护程序prio = 10 os_prio = 31 tid = 0x00007fdd6a004000 nid = 0x4b03在Object.wait()中[0x0000700010b94000] java.lang.Thread.State:在java.lang上等待(在对象监视器上)。 Object.wait(本机方法)-在java.lang.ref.Reference.tryHandlePending(Reference.java.lang.Object.wait(Object.java:502)上等待(java.lang.ref.Reference $ Lock)。 java:191)-锁定(java.lang.ref.Reference $ Lock)在java.lang.ref.Reference $ ReferenceHandler.run(Reference.java:153)

"主要"#1 prio = 5 os_prio = 31 tid = 0x00007fdd68801800 nid = 0x2403可运行[0x0000700010175000] java.lang.Thread.State:在java.net.Inet6AddressImpl.lookupAllHostAddr(本机方法)处为RUNNABLE。 位于java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)处的InetAddress $ 2.lookupAllHostAddr(InetAddress.java:929)位于java.net.InetAddress.getLocalHost(InetAddress.java:1501)-已锁定(java.lang.Object )在sun.rmi.transport.tcp.TCPEndpoint。(TCPEndpoint.java:113)在sun.rmi.transport.LiveRef。(LiveRef.java:103)在sun.rmi.transport.LiveRef。(LiveRef.java:85) )在sun.rmi.server.UnicastServerRef2(UnicastServerRef2.java:82)在sun.management.jmxremote.ConnectorBootstrap $ PermanentExporter.exportObject(ConnectorBootstrap.java:197)在javax.management.remote.rmi.RMIJRMPJServerServerImpl.export(R .java:146),位于javax.management.remote.rmi.RMIJRMPServerImpl.export(RMIJRMPServerImpl.java:122),位于javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:404) -在sun.management.Agent.startLocalManagementAgent(Agent.java:137)处锁定在sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:550)处(javax.management.remote.rmi.RMIConnectorServer)-锁定(a sun.management.Agent.startAgent(Agent.java:265)上的sun.management.Agent的java.lang.Class,sun.management.Agent.startAgent(Agent.java:452)

" VM线程" os_prio = 31 tid = 0x00007fdd67013800 nid = 0x2e03可运行

" GC任务线程#0(ParallelGC)" os_prio = 31 tid = 0x00007fdd6880d800 nid = 0x1c07可运行

" GC任务线程#1(ParallelGC)" os_prio = 31 tid = 0x00007fdd6880e000 nid = 0x1d03可运行

" GC任务线程#2(ParallelGC)" os_prio = 31 tid = 0x00007fdd6880e800 nid = 0x5403可运行

" GC任务线程#3(ParallelGC)" os_prio = 31 tid = 0x00007fdd6880f800 nid = 0x2b03可运行

" GC任务线程#4(ParallelGC)" os_prio = 31 tid = 0x00007fdd68810000 nid = 0x5103可运行

" GC任务线程#5(ParallelGC)" os_prio = 31 tid = 0x00007fdd68810800 nid = 0x2c03可运行

" GC任务线程#6(ParallelGC)" os_prio = 31 tid = 0x00007fdd68811000 nid = 0x2d03可运行

" GC任务线程#7(ParallelGC)" os_prio = 31 tid = 0x00007fdd68812000 nid = 0x4d03可运行

JNI全球参考文献:17

堆PSYoungGen总计76288K,已使用3932K [0x0000000795580000,0x000000079aa80000,0x00000007c0000000)伊甸园空间65536K,已使用6%的[0x0000000795580000,0x00000007959570c8,0x0000000799580000)从空间10752K,0%已使用[0x000000079a000000(0x000000079a000000) 已使用的百分比[0x0000000799580000,0x0000000799580000,0x000000079a000000)ParOldGen总计175104K,已使用0K [0x0000000740000000,0x000000074ab00000,0x0000000795580000)对象空间175104K,已使用0%[0x0000000740000000,0x0000000740000000,0x000000K283283,已保留容量5768504K28300000 已使用615K,容量616K,已提交640K,已预留1048576K

JVM没有根据请求退出,请求终止。 JVM收到信号SIGKILL(9)。 JVM进程不见了。 JVM被要求终止后退出。 重新加载包装器配置...

         点击此处--->   EasySAP.com群内免费提供SAP练习系统(在群公告中)

加入QQ群:457200227(SAP S4 HANA技术交流) 群内免费提供SAP练习系统(在群公告中)


在Tomcat上运行hybrisPlatform ...-> Wrapper作为控制台Java服务启动Wrapper专业版64位3.5.29版权所有(C)1999-2016 Tanuki Software,Ltd.保留所有权利。 http://wrapper.tanukisoftware.com 已获得针对hybris平台的SAP SE许可

启动JVM ...启动失败:等待JVM的信号超时。 转储JVM状态。 2019-05-05 16:28:56全线程转储Java HotSpot(TM)64位服务器VM(25.191-b12混合模式):

"服务线程"#9守护程序prio = 9 os_prio = 31 tid = 0x00007fdd6881f000 nid = 0x3d03 runnable [0x0000000000000000] java.lang.Thread.State:RUNNABLE

" C1 CompilerThread3"#8守护程序prio = 9 os_prio = 31 tid = 0x00007fdd6800a000 nid = 0x3e03等待条件[0x0000000000000000] java.lang.Thread.State:RUNNABLE

" C2 CompilerThread2"#7守护程序prio = 9 os_prio = 31 tid = 0x00007fdd68800000 nid = 0x3803等待条件[0x0000000000000000] java.lang.Thread.State:RUNNABLE

" C2 CompilerThread1"#6守护程序prio = 9 os_prio = 31 tid = 0x00007fdd68009000 nid = 0x3603等待条件[0x0000000000000000] java.lang.Thread.State:RUNNABLE

" C2 CompilerThread0"#5守护程序prio = 9 os_prio = 31 tid = 0x00007fdd67020000 nid = 0x4003等待条件[0x0000000000000000] java.lang.Thread.State:RUNNABLE

"信号分配器"#4守护程序prio = 9 os_prio = 31 tid = 0x00007fdd67824800 nid = 0x4203等待条件[0x0000000000000000] java.lang.Thread.State:RUNNABLE

" Finalizer"#3守护程序prio = 8 os_prio = 31 tid = 0x00007fdd67805800 nid = 0x4903 in Object.wait()[0x0000700010c97000] java.lang.Thread.State:在java.lang.Object上等待(在对象监视器上) .wait(本机方法)-在java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)上等待(java.lang.ref.ReferenceQueue $ Lock)-锁定(java.lang.ref.ReferenceQueue $ 锁定)在java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)在java.lang.ref.Finalizer $ FinalizerThread.run(Finalizer.java:216)

"引用处理程序"#2守护程序prio = 10 os_prio = 31 tid = 0x00007fdd6a004000 nid = 0x4b03在Object.wait()中[0x0000700010b94000] java.lang.Thread.State:在java.lang上等待(在对象监视器上)。 Object.wait(本机方法)-在java.lang.ref.Reference.tryHandlePending(Reference.java.lang.Object.wait(Object.java:502)上等待(java.lang.ref.Reference $ Lock)。 java:191)-锁定(java.lang.ref.Reference $ Lock)在java.lang.ref.Reference $ ReferenceHandler.run(Reference.java:153)

"主要"#1 prio = 5 os_prio = 31 tid = 0x00007fdd68801800 nid = 0x2403可运行[0x0000700010175000] java.lang.Thread.State:在java.net.Inet6AddressImpl.lookupAllHostAddr(本机方法)处为RUNNABLE。 位于java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)处的InetAddress $ 2.lookupAllHostAddr(InetAddress.java:929)位于java.net.InetAddress.getLocalHost(InetAddress.java:1501)-已锁定(java.lang.Object )在sun.rmi.transport.tcp.TCPEndpoint。(TCPEndpoint.java:113)在sun.rmi.transport.LiveRef。(LiveRef.java:103)在sun.rmi.transport.LiveRef。(LiveRef.java:85) )在sun.rmi.server.UnicastServerRef2(UnicastServerRef2.java:82)在sun.management.jmxremote.ConnectorBootstrap $ PermanentExporter.exportObject(ConnectorBootstrap.java:197)在javax.management.remote.rmi.RMIJRMPJServerServerImpl.export(R .java:146),位于javax.management.remote.rmi.RMIJRMPServerImpl.export(RMIJRMPServerImpl.java:122),位于javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:404) -在sun.management.Agent.startLocalManagementAgent(Agent.java:137)处锁定在sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:550)处(javax.management.remote.rmi.RMIConnectorServer)-锁定(a sun.management.Agent.startAgent(Agent.java:265)上的sun.management.Agent的java.lang.Class,sun.management.Agent.startAgent(Agent.java:452)

" VM线程" os_prio = 31 tid = 0x00007fdd67013800 nid = 0x2e03可运行

" GC任务线程#0(ParallelGC)" os_prio = 31 tid = 0x00007fdd6880d800 nid = 0x1c07可运行

" GC任务线程#1(ParallelGC)" os_prio = 31 tid = 0x00007fdd6880e000 nid = 0x1d03可运行

" GC任务线程#2(ParallelGC)" os_prio = 31 tid = 0x00007fdd6880e800 nid = 0x5403可运行

" GC任务线程#3(ParallelGC)" os_prio = 31 tid = 0x00007fdd6880f800 nid = 0x2b03可运行

" GC任务线程#4(ParallelGC)" os_prio = 31 tid = 0x00007fdd68810000 nid = 0x5103可运行

" GC任务线程#5(ParallelGC)" os_prio = 31 tid = 0x00007fdd68810800 nid = 0x2c03可运行

" GC任务线程#6(ParallelGC)" os_prio = 31 tid = 0x00007fdd68811000 nid = 0x2d03可运行

" GC任务线程#7(ParallelGC)" os_prio = 31 tid = 0x00007fdd68812000 nid = 0x4d03可运行

JNI全球参考文献:17

堆PSYoungGen总计76288K,已使用3932K [0x0000000795580000,0x000000079aa80000,0x00000007c0000000)伊甸园空间65536K,已使用6%的[0x0000000795580000,0x00000007959570c8,0x0000000799580000)从空间10752K,0%已使用[0x000000079a000000(0x000000079a000000) 已使用的百分比[0x0000000799580000,0x0000000799580000,0x000000079a000000)ParOldGen总计175104K,已使用0K [0x0000000740000000,0x000000074ab00000,0x0000000795580000)对象空间175104K,已使用0%[0x0000000740000000,0x0000000740000000,0x000000K283283,已保留容量5768504K28300000 已使用615K,容量616K,已提交640K,已预留1048576K

JVM没有根据请求退出,请求终止。 JVM收到信号SIGKILL(9)。 JVM进程不见了。 JVM被要求终止后退出。 重新加载包装器配置...

付费偷看设置
发送
1条回答
CJones
1楼-- · 2020-09-09 05:52

Hi-通常,这是由于缺少系统资源(内存,CPU等)而发生的。 请检查您的系统配置是否与系统要求兼容,例如