javax.management.InstanceAlreadyExistsException: com.datastax.driver.core:type=Errors,name=write-timeouts

DataStax JIRA | Michael Los | 4 years ago
  1. 0

    I was allowing for the possibility of creating more than one Cluster (with different policy settings) and noticed the stack trace below. Everything seems to function, but the stack trace makes me wonder whether multiple Cluster instances are expected as typical use. This unit test will trigger the stack trace. {CODE} @Test public final void testMultipleCluster() { Cluster c1 = new Cluster.Builder().addContactPoint("127.0.0.1").build(); assertNotNull(c1); Cluster c2 = new Cluster.Builder().addContactPoint("127.0.0.1").build(); assertNotNull(c2); } {CODE} Note that the test succeeds, but the attached stack trace is generated. (It's long). The first part follows: {CODE} 19:24:25.010 [main] WARN c.y.m.r.JmxReporter - Error processing com.datastax.driver.core:type=Errors,name=write-timeouts javax.management.InstanceAlreadyExistsException: com.datastax.driver.core:type=Errors,name=write-timeouts at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) ~[na:1.7.0_17] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) ~[na:1.7.0_17] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) ~[na:1.7.0_17] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) ~[na:1.7.0_17] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) ~[na:1.7.0_17] at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:513) ~[na:1.7.0_17] at com.yammer.metrics.reporting.JmxReporter.registerBean(JmxReporter.java:451) [metrics-core-2.0.3.jar:na] at com.yammer.metrics.reporting.JmxReporter.processCounter(JmxReporter.java:409) [metrics-core-2.0.3.jar:na] at com.yammer.metrics.reporting.JmxReporter.processCounter(JmxReporter.java:16) [metrics-core-2.0.3.jar:na] at com.yammer.metrics.core.Counter.processWith(Counter.java:65) ~[metrics-core-2.0.3.jar:na] at com.yammer.metrics.reporting.JmxReporter.onMetricAdded(JmxReporter.java:386) [metrics-core-2.0.3.jar:na] at com.yammer.metrics.core.MetricsRegistry.addListener(MetricsRegistry.java:442) [metrics-core-2.0.3.jar:na] at com.yammer.metrics.reporting.JmxReporter.start(JmxReporter.java:446) [metrics-core-2.0.3.jar:na] at com.datastax.driver.core.Metrics.<init>(Metrics.java:76) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at com.datastax.driver.core.Cluster$Manager.<init>(Cluster.java:514) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at com.datastax.driver.core.Cluster$Manager.<init>(Cluster.java:473) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at com.datastax.driver.core.Cluster.<init>(Cluster.java:65) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at com.datastax.driver.core.Cluster.buildFrom(Cluster.java:93) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at com.datastax.driver.core.Cluster$Builder.build(Cluster.java:458) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at prim.msgHandler.persister.cassjava.SessionFactoryBeanTest.testMultipleCluster(SessionFactoryBeanTest.java:64) [test-classes/:na] {CODE}

    DataStax JIRA | 4 years ago | Michael Los
    javax.management.InstanceAlreadyExistsException: com.datastax.driver.core:type=Errors,name=write-timeouts
  2. 0

    I was allowing for the possibility of creating more than one Cluster (with different policy settings) and noticed the stack trace below. Everything seems to function, but the stack trace makes me wonder whether multiple Cluster instances are expected as typical use. This unit test will trigger the stack trace. {CODE} @Test public final void testMultipleCluster() { Cluster c1 = new Cluster.Builder().addContactPoint("127.0.0.1").build(); assertNotNull(c1); Cluster c2 = new Cluster.Builder().addContactPoint("127.0.0.1").build(); assertNotNull(c2); } {CODE} Note that the test succeeds, but the attached stack trace is generated. (It's long). The first part follows: {CODE} 19:24:25.010 [main] WARN c.y.m.r.JmxReporter - Error processing com.datastax.driver.core:type=Errors,name=write-timeouts javax.management.InstanceAlreadyExistsException: com.datastax.driver.core:type=Errors,name=write-timeouts at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) ~[na:1.7.0_17] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) ~[na:1.7.0_17] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) ~[na:1.7.0_17] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) ~[na:1.7.0_17] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) ~[na:1.7.0_17] at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:513) ~[na:1.7.0_17] at com.yammer.metrics.reporting.JmxReporter.registerBean(JmxReporter.java:451) [metrics-core-2.0.3.jar:na] at com.yammer.metrics.reporting.JmxReporter.processCounter(JmxReporter.java:409) [metrics-core-2.0.3.jar:na] at com.yammer.metrics.reporting.JmxReporter.processCounter(JmxReporter.java:16) [metrics-core-2.0.3.jar:na] at com.yammer.metrics.core.Counter.processWith(Counter.java:65) ~[metrics-core-2.0.3.jar:na] at com.yammer.metrics.reporting.JmxReporter.onMetricAdded(JmxReporter.java:386) [metrics-core-2.0.3.jar:na] at com.yammer.metrics.core.MetricsRegistry.addListener(MetricsRegistry.java:442) [metrics-core-2.0.3.jar:na] at com.yammer.metrics.reporting.JmxReporter.start(JmxReporter.java:446) [metrics-core-2.0.3.jar:na] at com.datastax.driver.core.Metrics.<init>(Metrics.java:76) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at com.datastax.driver.core.Cluster$Manager.<init>(Cluster.java:514) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at com.datastax.driver.core.Cluster$Manager.<init>(Cluster.java:473) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at com.datastax.driver.core.Cluster.<init>(Cluster.java:65) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at com.datastax.driver.core.Cluster.buildFrom(Cluster.java:93) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at com.datastax.driver.core.Cluster$Builder.build(Cluster.java:458) [cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na] at prim.msgHandler.persister.cassjava.SessionFactoryBeanTest.testMultipleCluster(SessionFactoryBeanTest.java:64) [test-classes/:na] {CODE}

    DataStax JIRA | 4 years ago | Michael Los
    javax.management.InstanceAlreadyExistsException: com.datastax.driver.core:type=Errors,name=write-timeouts
  3. 0

    These warnings, I would imagine, are harmless, but they are filling up my server.log. A warning should take up only one or two lines, and not throw a length stack trace that is of little use to anyone. I read here ( https://datastax-oss.atlassian.net/browse/JAVA-74) that Metrics -- the cause -- can be disabled to get rid of the warning but I need Metrics. The stack trace below is just one of several same warning thrown. 16:34:57,641 WARN [com.yammer.metrics.reporting.JmxReporter] (MSC service thread 1-8) Error processing com.datastax.driver.core:type=Errors,name=write-timeouts: javax.management.InstanceAlreadyExistsException: com.datastax.driver.core:type=Errors,name=write-timeouts at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) [rt.jar:1.7.0_21] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) [rt.jar:1.7.0_21] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) [rt.jar:1.7.0_21] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) [rt.jar:1.7.0_21] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) [rt.jar:1.7.0_21] at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:513) [rt.jar:1.7.0_21] at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.java:551) at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:319) at com.yammer.metrics.reporting.JmxReporter.registerBean(JmxReporter.java:451) [metrics-core-2.0.3.jar:] at com.yammer.metrics.reporting.JmxReporter.processCounter(JmxReporter.java:409) [metrics-core-2.0.3.jar:] at com.yammer.metrics.reporting.JmxReporter.processCounter(JmxReporter.java:16) [metrics-core-2.0.3.jar:] at com.yammer.metrics.core.Counter.processWith(Counter.java:65) [metrics-core-2.0.3.jar:] at com.yammer.metrics.reporting.JmxReporter.onMetricAdded(JmxReporter.java:386) [metrics-core-2.0.3.jar:] at com.yammer.metrics.core.MetricsRegistry.addListener(MetricsRegistry.java:442) [metrics-core-2.0.3.jar:] at com.yammer.metrics.reporting.JmxReporter.start(JmxReporter.java:446) [metrics-core-2.0.3.jar:] at com.datastax.driver.core.Metrics.<init>(Metrics.java:76) [cassandra-driver-core.jar:] at com.datastax.driver.core.Cluster$Manager.<init>(Cluster.java:544) [cassandra-driver-core.jar:] at com.datastax.driver.core.Cluster$Manager.<init>(Cluster.java:503) [cassandra-driver-core.jar:] at com.datastax.driver.core.Cluster.<init>(Cluster.java:65) [cassandra-driver-core.jar:] at com.datastax.driver.core.Cluster.buildFrom(Cluster.java:93) [cassandra-driver-core.jar:] at com.datastax.driver.core.Cluster$Builder.build(Cluster.java:484) [cassandra-driver-core.jar:] at com.xxxxxx.xxx.dao.utils.PersistentUnit$CCluster.<init>(PersistentUnit.java:423) [xxx-dao.jar:] at com.xxxxxx.xxx.dao.utils.PersistentUnit$CCluster.create(PersistentUnit.java:408) [xxx-dao.jar:] at com.xxxxxx.xxx.dao.utils.PersistentUnit.buildCluster(PersistentUnit.java:85) [xxx-dao.jar:] at com.xxxxxx.xxx.dao.utils.PersistentUnit.getSession(PersistentUnit.java:96) [xxx-dao.jar:] at com.xxxxxx.xxx.dao.utils.PersistentUnit.getSession(PersistentUnit.java:126) [xxx-dao.jar:] at com.xxxxxx.xxx.dao.repository.AbstractRepository.<clinit>(AbstractRepository.java:108) [xxx-dao.jar:] at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_21] at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_21]

    DataStax JIRA | 4 years ago | Benjamin Seyinbour
    javax.management.InstanceAlreadyExistsException: com.datastax.driver.core:type=Errors,name=write-timeouts
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    These warnings, I would imagine, are harmless, but they are filling up my server.log. A warning should take up only one or two lines, and not throw a length stack trace that is of little use to anyone. I read here ( https://datastax-oss.atlassian.net/browse/JAVA-74) that Metrics -- the cause -- can be disabled to get rid of the warning but I need Metrics. The stack trace below is just one of several same warning thrown. 16:34:57,641 WARN [com.yammer.metrics.reporting.JmxReporter] (MSC service thread 1-8) Error processing com.datastax.driver.core:type=Errors,name=write-timeouts: javax.management.InstanceAlreadyExistsException: com.datastax.driver.core:type=Errors,name=write-timeouts at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) [rt.jar:1.7.0_21] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) [rt.jar:1.7.0_21] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) [rt.jar:1.7.0_21] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) [rt.jar:1.7.0_21] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) [rt.jar:1.7.0_21] at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:513) [rt.jar:1.7.0_21] at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.java:551) at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:319) at com.yammer.metrics.reporting.JmxReporter.registerBean(JmxReporter.java:451) [metrics-core-2.0.3.jar:] at com.yammer.metrics.reporting.JmxReporter.processCounter(JmxReporter.java:409) [metrics-core-2.0.3.jar:] at com.yammer.metrics.reporting.JmxReporter.processCounter(JmxReporter.java:16) [metrics-core-2.0.3.jar:] at com.yammer.metrics.core.Counter.processWith(Counter.java:65) [metrics-core-2.0.3.jar:] at com.yammer.metrics.reporting.JmxReporter.onMetricAdded(JmxReporter.java:386) [metrics-core-2.0.3.jar:] at com.yammer.metrics.core.MetricsRegistry.addListener(MetricsRegistry.java:442) [metrics-core-2.0.3.jar:] at com.yammer.metrics.reporting.JmxReporter.start(JmxReporter.java:446) [metrics-core-2.0.3.jar:] at com.datastax.driver.core.Metrics.<init>(Metrics.java:76) [cassandra-driver-core.jar:] at com.datastax.driver.core.Cluster$Manager.<init>(Cluster.java:544) [cassandra-driver-core.jar:] at com.datastax.driver.core.Cluster$Manager.<init>(Cluster.java:503) [cassandra-driver-core.jar:] at com.datastax.driver.core.Cluster.<init>(Cluster.java:65) [cassandra-driver-core.jar:] at com.datastax.driver.core.Cluster.buildFrom(Cluster.java:93) [cassandra-driver-core.jar:] at com.datastax.driver.core.Cluster$Builder.build(Cluster.java:484) [cassandra-driver-core.jar:] at com.xxxxxx.xxx.dao.utils.PersistentUnit$CCluster.<init>(PersistentUnit.java:423) [xxx-dao.jar:] at com.xxxxxx.xxx.dao.utils.PersistentUnit$CCluster.create(PersistentUnit.java:408) [xxx-dao.jar:] at com.xxxxxx.xxx.dao.utils.PersistentUnit.buildCluster(PersistentUnit.java:85) [xxx-dao.jar:] at com.xxxxxx.xxx.dao.utils.PersistentUnit.getSession(PersistentUnit.java:96) [xxx-dao.jar:] at com.xxxxxx.xxx.dao.utils.PersistentUnit.getSession(PersistentUnit.java:126) [xxx-dao.jar:] at com.xxxxxx.xxx.dao.repository.AbstractRepository.<clinit>(AbstractRepository.java:108) [xxx-dao.jar:] at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_21] at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_21]

    DataStax JIRA | 4 years ago | Benjamin Seyinbour
    javax.management.InstanceAlreadyExistsException: com.datastax.driver.core:type=Errors,name=write-timeouts
  6. 0

    Grails ActiveMQ javax.management.InstanceAlreadyExistsException

    Stack Overflow | 2 years ago | Carlos Eduardo
    javax.management.InstanceAlreadyExistsException: org.apache.activemq:BrokerName=localhost,Type=Broker

  1. batwalrus76 2 times, last 2 weeks ago
  2. Handemelindo 1 times, last 2 weeks ago
  3. kjhdofjosvs 2 times, last 3 weeks ago
  4. tvrmsmith 2 times, last 1 month ago
  5. davidvanlaatum 54 times, last 2 months ago
3 more registered users
21 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. javax.management.InstanceAlreadyExistsException

    com.datastax.driver.core:type=Errors,name=write-timeouts

    at com.sun.jmx.mbeanserver.Repository.addMBean()
  2. Java RT
    JmxMBeanServer.registerMBean
    1. com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)[na:1.7.0_17]
    2. com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)[na:1.7.0_17]
    3. com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)[na:1.7.0_17]
    4. com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)[na:1.7.0_17]
    5. com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)[na:1.7.0_17]
    6. com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:513)[na:1.7.0_17]
    6 frames
  3. com.yammer.metrics
    JmxReporter.processCounter
    1. com.yammer.metrics.reporting.JmxReporter.registerBean(JmxReporter.java:451)[metrics-core-2.0.3.jar:na]
    2. com.yammer.metrics.reporting.JmxReporter.processCounter(JmxReporter.java:409)[metrics-core-2.0.3.jar:na]
    3. com.yammer.metrics.reporting.JmxReporter.processCounter(JmxReporter.java:16)[metrics-core-2.0.3.jar:na]
    3 frames
  4. Apache Giraph Core
    Counter.processWith
    1. com.yammer.metrics.core.Counter.processWith(Counter.java:65)[metrics-core-2.0.3.jar:na]
    1 frame
  5. com.yammer.metrics
    JmxReporter.onMetricAdded
    1. com.yammer.metrics.reporting.JmxReporter.onMetricAdded(JmxReporter.java:386)[metrics-core-2.0.3.jar:na]
    1 frame
  6. Apache Giraph Core
    MetricsRegistry.addListener
    1. com.yammer.metrics.core.MetricsRegistry.addListener(MetricsRegistry.java:442)[metrics-core-2.0.3.jar:na]
    1 frame
  7. com.yammer.metrics
    JmxReporter.start
    1. com.yammer.metrics.reporting.JmxReporter.start(JmxReporter.java:446)[metrics-core-2.0.3.jar:na]
    1 frame
  8. DataStax Java Driver for Apache Cassandra - Core
    Cluster$Builder.build
    1. com.datastax.driver.core.Metrics.<init>(Metrics.java:76)[cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na]
    2. com.datastax.driver.core.Cluster$Manager.<init>(Cluster.java:514)[cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na]
    3. com.datastax.driver.core.Cluster$Manager.<init>(Cluster.java:473)[cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na]
    4. com.datastax.driver.core.Cluster.<init>(Cluster.java:65)[cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na]
    5. com.datastax.driver.core.Cluster.buildFrom(Cluster.java:93)[cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na]
    6. com.datastax.driver.core.Cluster$Builder.build(Cluster.java:458)[cassandra-driver-core-1.0.0-beta3-SNAPSHOT.jar:na]
    6 frames
  9. prim.msgHandler.persister
    SessionFactoryBeanTest.testMultipleCluster
    1. prim.msgHandler.persister.cassjava.SessionFactoryBeanTest.testMultipleCluster(SessionFactoryBeanTest.java:64)[test-classes/:na]
    1 frame