You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Preeti Gupta (Jira)" <ji...@apache.org> on 2020/07/28 17:51:00 UTC
[jira] [Commented] (NIFI-1559) Kafka processor writes some WARN
message about registering an Mbean
[ https://issues.apache.org/jira/browse/NIFI-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166596#comment-17166596 ]
Preeti Gupta commented on NIFI-1559:
------------------------------------
hi,
Are there any updates on this? I am also seeing same issue.
> Kafka processor writes some WARN message about registering an Mbean
> -------------------------------------------------------------------
>
> Key: NIFI-1559
> URL: https://issues.apache.org/jira/browse/NIFI-1559
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.5.0
> Reporter: Joe Witt
> Priority: Minor
>
> The kafka processors on startup appear to log a WARN about Mbean registration. This is at least alarming to a DFM.
> {quote}
> 2016-02-23 21:13:56,813 WARN [pool-29-thread-5] o.a.kafka.common.utils.AppInfoParser Error registering AppInfo mbean
> javax.management.InstanceAlreadyExistsException: kafka.producer:type=app-info,id=NiFi-2243c3f9-bd2b-4bfe-b515-09791ec25c4c
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) ~[na:1.8.0_65]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) ~[na:1.8.0_65]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) ~[na:1.8.0_65]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) ~[na:1.8.0_65]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) ~[na:1.8.0_65]
> at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) ~[na:1.8.0_65]
> at org.apache.kafka.common.utils.AppInfoParser.registerAppInfo(AppInfoParser.java:57) ~[kafka-clients-0.9.0.0.jar:na]
> at org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:314) [kafka-clients-0.9.0.0.jar:na]
> at org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:194) [kafka-clients-0.9.0.0.jar:na]
> at org.apache.nifi.processors.kafka.PutKafka.createProducer(PutKafka.java:325) [nifi-kafka-processors-0.5.1.jar:0.5.1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_65]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_65]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_65]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_65]
> at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:102) [nifi-framework-core-0.5.1-SNAPSHOT.jar:0.5.1]
> at org.apache.nifi.controller.scheduling.StandardProcessScheduler$4.run(StandardProcessScheduler.java:366) [nifi-framework-core-0.5.1-SNAPSHOT.jar:0.5.1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_65]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_65]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_65]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_65]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_65]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)