Details
-
Bug
-
Resolution: Done
-
Critical
-
0.2
-
None
Description
Starting the MySQL connector produces the following warning about a duplicate AppInfo mbean:
[2016-09-15 17:39:27,055] WARN Error registering AppInfo mbean (org.apache.kafka.common.utils.AppInfoParser:60)
javax.management.InstanceAlreadyExistsException: kafka.producer:type=app-info,id=b29b0d29-bbd9-469e-985f-594fc8662adc
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
at org.apache.kafka.common.utils.AppInfoParser.registerAppInfo(AppInfoParser.java:58)
at org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:328)
at org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:188)
at io.debezium.relational.history.KafkaDatabaseHistory.start(KafkaDatabaseHistory.java:147)
at io.debezium.connector.mysql.MySqlSchema.start(MySqlSchema.java:134)
at io.debezium.connector.mysql.MySqlTaskContext.start(MySqlTaskContext.java:135)
at io.debezium.connector.mysql.MySqlConnectorTask.start(MySqlConnectorTask.java:69)
at org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:137)
at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:140)
at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:175)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
The mbean ID appears to be set with the Kafka producer's client.id, so I think we just need to set this to a unique value within the KafkaDatabaseHistory class.
Attachments
Issue Links
- relates to
-
DBZ-115 Producer does not send any new events to Kafka after snapshot when using MySQL 5.5
-
- Closed
-
