首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >ignite服务器出现一些与线程相关的异常

问ignite服务器出现一些与线程相关的异常
EN

Stack Overflow用户
提问于 2019-09-14 03:30:31
回答 1查看 485关注 0票数 0

其中一个ignite服务器提供了一些线程相关的exception.Below是一些stackTrace:

谁能告诉我为什么这些线程相关的异常会出现。当另一个具有相同服务器实例名称的服务器启动时,我收到此错误。我知道服务器正在被关闭,因为上面的reason.But,为什么这些线程相关的错误来了。我还在最后发布了ignite服务器的java代码。

代码语言:javascript
复制
Thread [name="ignite-update-notifier-timer", id=96, state=TIMED_WAITING, blockCnt=0, waitCnt=1]
    at java.base@11.0.2/java.lang.Thread.sleep(Native Method)
    at app//o.a.i.i.processors.cluster.ClusterProcessor$UpdateNotifierTimerTask.safeRun(ClusterProcessor.java:707)
    at app//o.a.i.i.util.GridTimerTask.run(GridTimerTask.java:33)
    at java.base@11.0.2/java.util.TimerThread.mainLoop(Timer.java:556)
    at java.base@11.0.2/java.util.TimerThread.run(Timer.java:506)

Thread [name="exchange-worker-#43%CcPlatformUserRolesOrganizationAssociationServerGroupUsers%", id=97, state=RUNNABLE, blockCnt=97, waitCnt=1]
    at java.management@11.0.2/sun.management.ThreadImpl.dumpThreads0(Native Method)
    at java.management@11.0.2/sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:502)
    at java.management@11.0.2/sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:490)
    at app//o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1391)
    at app//o.a.i.i.processors.failure.FailureProcessor.process(FailureProcessor.java:143)
    - locked o.a.i.i.processors.failure.FailureProcessor@44d9dc1c
    at app//o.a.i.i.processors.failure.FailureProcessor.process(FailureProcessor.java:112)
    at app//o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2924)
    at app//o.a.i.i.util.worker.GridWorker.run(GridWorker.java:119)
    at java.base@11.0.2/java.lang.Thread.run(Thread.java:834)

Thread [name="sys-#44%CcPlatformUserRolesOrganizationAssociationServerGroupUsers%", id=98, state=TIMED_WAITING, blockCnt=80, waitCnt=1]
Lock [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@74fe8ae1, ownerName=null, ownerId=-1]
    at java.base@11.0.2/jdk.internal.misc.Unsafe.park(Native Method)
    at java.base@11.0.2/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
    at java.base@11.0.2/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
    at java.base@11.0.2/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
    at java.base@11.0.2/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1053)
    at java.base@11.0.2/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
    at java.base@11.0.2/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base@11.0.2/java.lang.Thread.run(Thread.java:834)

Thread [name="sys-#45%CcPlatformUserRolesOrganizationAssociationServerGroupUsers%", id=99, state=TIMED_WAITING, blockCnt=52, waitCnt=1]
Lock [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@74fe8ae1, ownerName=null, ownerId=-1]
    at java.base@11.0.2/jdk.internal.misc.Unsafe.park(Native Method)
    at java.base@11.0.2/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
    at java.base@11.0.2/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
    at java.base@11.0.2/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
    at java.base@11.0.2/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1053)
    at java.base@11.0.2/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
    at java.base@11.0.2/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base@11.0.2/java.lang.Thread.run(Thread.java:834)

Thread [name="sys-#46%CcPlatformUserRolesOrganizationAssociationServerGroupUsers%", id=100, state=TIMED_WAITING, blockCnt=0, waitCnt=1]
Lock [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@74fe8ae1, ownerName=null, ownerId=-1]
    at java.base@11.0.2/jdk.internal.misc.Unsafe.park(Native Method)
    at java.base@11.0.2/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
    at java.base@11.0.2/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
    at java.base@11.0.2/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
    at java.base@11.0.2/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1053)
    at java.base@11.0.2/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
    at java.base@11.0.2/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base@11.0.2/java.lang.Thread.run(Thread.java:834)

以下是Ignite服务器代码。

代码语言:javascript
复制
public IgniteConfiguration createConfiguration() throws Exception {
    IgniteConfiguration cfg = new IgniteConfiguration();

    cfg.setIgniteInstanceName("CcPlatformUserRolesOrganizationAssociationServerGroups");
    cfg.setSqlSchemas("public");
    TcpDiscoverySpi discovery = new TcpDiscoverySpi();

    TcpDiscoveryMulticastIpFinder ipFinder = new TcpDiscoveryMulticastIpFinder();

    ipFinder.setAddresses(Arrays.asList("127.0.0.1:47500..47510"));

    discovery.setIpFinder(ipFinder);

    cfg.setDiscoverySpi(discovery);
    cfg.setPeerClassLoadingEnabled(true);
    // setting Cache
    cfg.setCacheConfiguration(cacheGroupsCache());

    return cfg;
}
EN

回答 1

Stack Overflow用户

回答已采纳

发布于 2019-09-14 04:18:55

这些不是异常或错误。它是一个线程转储,显示JVM中每个线程在特定时刻的活动和状态。Ignite配置为在检测到故障时自动记录线程转储。您可以使用IGNITE_DUMP_THREADS_ON_FAILURE系统属性来更改这一点。更多信息请点击此处:https://apacheignite.readme.io/docs/logging

票数 2
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/57929395

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档