jmxConfigurator - reload kills JMXBean

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: unspecified
  • Fix Version/s: 0.9.12
  • Component/s: Other
  • Labels:
    None
  • Environment:
    Operating System: All
    Platform: All
  • Bugzilla Id:
    41

Description

add <jmxConfigurator /> to your configuration

add "-Dcom.sun.management.jmxremote" to your program args

open jconsole

invoke operation reload on ch.qos.logback.classic/default/ch.qos.logback.classic.jmx.Configuration

=> bean will be removed from the MBean list but will not be re-added

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Sebastian Davids added a comment -
Logback 0.9
Show
Sebastian Davids added a comment - Logback 0.9
Hide
Permalink
Sébastien Pennec added a comment -
Hello Sebastian,

I'm having a hard time reproducing this bug.
I've used the class and configuration that you included in the LBCLASSIC-15.

If I hit the reload button (the one which does not take any parameter), then the configuration is reloaded (I see the info messages coming each 5 seconds).
If I invoke the other reload method, specifying a working path, it also works: I can see the configuration changes. Lastly, if I invoke this method with an incorrect path, then an error pops out (which might be better managed, I must admit) and everything stops, until either I specify a valid path or hit the other reload button.

Can you help me a bit more on this bug? :)

Thanks for you reports!

Sébastien
Show
Sébastien Pennec added a comment - Hello Sebastian, I'm having a hard time reproducing this bug. I've used the class and configuration that you included in the LBCLASSIC-15. If I hit the reload button (the one which does not take any parameter), then the configuration is reloaded (I see the info messages coming each 5 seconds). If I invoke the other reload method, specifying a working path, it also works: I can see the configuration changes. Lastly, if I invoke this method with an incorrect path, then an error pops out (which might be better managed, I must admit) and everything stops, until either I specify a valid path or hit the other reload button. Can you help me a bit more on this bug? :) Thanks for you reports! Sébastien
Hide
Permalink
Joern Huxhorn added a comment -
I think this problem might be fixed by http://jira.qos.ch/browse/LBCLASSIC-51
Show
Joern Huxhorn added a comment - I think this problem might be fixed by http://jira.qos.ch/browse/LBCLASSIC-51

People

  • Assignee:
    Logback dev list
    Reporter:
    Sebastian Davids
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: