[jira] [Created] (FLUME-2310) after reloading configuration at runtime, JMX monitoring metrics doesn't updates without restarting flume.

["minseok kim (JIRA)" <ji...@apache.org>]

minseok kim created FLUME-2310:
----------------------------------

             Summary: after reloading configuration at runtime, JMX monitoring metrics doesn't updates without restarting flume. 
                 Key: FLUME-2310
                 URL: https://issues.apache.org/jira/browse/FLUME-2310
             Project: Flume
          Issue Type: Bug
          Components: Configuration
    Affects Versions: v1.4.0
         Environment: centos 6.3
            Reporter: minseok kim
            Priority: Minor


flume provides JMX monitoring interface by following extra arguments.
-Dflume.monitoring.type=http -Dflume.monitoring.port=
and user can monitor flume via web browser.

after flume reloading its configuration at runtime, related jmx metrics doesn't automatically with following error log.

log says that error occurs when re-registering MBean to JMXServer because of the already registered MBean.

regardless of this error, other feature such as gathering log still works.

---------------------------------------------
2014/02/04 15:33:17,997/KST ERROR lifecycleSupervisor-1-2 - Failed to register monitored counter group for type: CHANNEL, name: channel1 (instrumentation.MonitoredCounterGroup.register:113)
javax.management.InstanceAlreadyExistsException: org.apache.flume.channel:type=channel1
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:108)
at org.apache.flume.instrumentation.MonitoredCounterGroup.start(MonitoredCounterGroup.java:88)
at org.apache.flume.channel.file.FileChannel.start(FileChannel.java:319)
at org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
2014/02/04 15:33:17,999/KST  INFO lifecycleSupervisor-1-2 - Component type: CHANNEL, name: channel1 started 







--
This message was sent by Atlassian JIRA
(v6.1.5#6160)