cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-9019) GCInspector detected GC before ThreadPools are initialized
Date Mon, 23 Mar 2015 16:43:12 GMT
Philip Thompson created CASSANDRA-9019:
------------------------------------------

             Summary: GCInspector detected GC before ThreadPools are initialized
                 Key: CASSANDRA-9019
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9019
             Project: Cassandra
          Issue Type: Bug
            Reporter: Philip Thompson
            Assignee: Yuki Morishita
             Fix For: 3.0


While running the dtest {{one_all_test (consistency_test.TestConsistency)}}, I ran into the
following exception:
{code}


java.lang.RuntimeException: Error reading: org.apache.cassandra.metrics:type=ThreadPools,path=request,scope=ReadStage,name=ActiveTasks
        at org.apache.cassandra.metrics.ThreadPoolMetrics.getJmxMetric(ThreadPoolMetrics.java:134)
        at org.apache.cassandra.utils.StatusLogger.log(StatusLogger.java:55)
        at org.apache.cassandra.service.GCInspector.handleNotification(GCInspector.java:147)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1754)
        at sun.management.NotificationEmitterSupport.sendNotification(NotificationEmitterSupport.java:156)
        at sun.management.GarbageCollectorImpl.createGCNotification(GarbageCollectorImpl.java:150)
Caused by: java.lang.reflect.UndeclaredThrowableException
        at com.sun.proxy.$Proxy3.getValue(Unknown Source)
        at org.apache.cassandra.metrics.ThreadPoolMetrics.getJmxMetric(ThreadPoolMetrics.java:123)
        ... 5 more
Caused by: javax.management.InstanceNotFoundException: org.apache.cassandra.metrics:type=ThreadPools,path=request,scope=ReadStage,name=ActiveTasks
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:643)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678)
        at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:267)
        ... 7 more
    

{code}

Dtest didn't preserve the logs, which implies that this wasn't in the system.log, but printed
to stderr somehow, it's unclear with all the piping dtest and ccm do. I have yet to reproduce
the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message