I believe this is a WebSphere issue.

When you configure Logback to use <jmxConfigurator/> tag, it does deploy a JMX MBean....but for some reason, within WebSphere, it does not show up when using jConsole.

But it is deployed, and it can be accessed by other programmatic ways.

Here is a recent post that contains a code sample of how I am accessing it via Java code:

http://mailman.qos.ch/pipermail/logback-user/2012-March/003034.html


Thanks,
-Chris




From:        Pietro <pierre.morvant@gmail.com>
To:        logback-user@qos.ch
Date:        06/06/2012 10:55 AM
Subject:        Re: [logback-user] Websphere specific JMX configuration?
Sent by:        logback-user-bounces@qos.ch

---

Sumanth Donthi <thetallman63@...> writes:

>
>
>
> How can we enable JMX for logback in WebSphere ? Currently do not
see ch.qos.logback.classic.jmx.Configurator in jconsole though
>
>
> <jmxConfigurator/> tag exist in logback configuration file.
>
> logback 0.9.27WebSphere 7.0
>
> This is similar to one posted earlier -- http://www.qos.ch/pipermail/logback-
user/2010-November/001886.html
>
>
> -Sumanth
>
>
>
>
> _______________________________________________
> Logback-user mailing list
> Logback-user@...
> http://qos.ch/mailman/listinfo/logback-user
>

Hey !
I am looking for the same answer !
This bug is due to logback or websphere ?

Thanks for your help

Pietro

_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-user
*************************** IMPORTANT NOTE*****************************-- The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman & Co., its subsidiaries and affiliates ("BBH"). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus. ********************************************************************************