You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2015/10/11 17:33:05 UTC

[jira] [Updated] (DERBY-6816) JMX Garbage collection

     [ https://issues.apache.org/jira/browse/DERBY-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-6816:
---------------------------------
    Fix Version/s:     (was: 10.12.1.1)
                   10.12.1.2

> JMX Garbage collection
> ----------------------
>
>                 Key: DERBY-6816
>                 URL: https://issues.apache.org/jira/browse/DERBY-6816
>             Project: Derby
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 10.11.1.1
>         Environment: Linux
>            Reporter: sagar
>             Fix For: 10.12.1.2
>
>
> When I use JMX remote and use Jconsole ... I click on Force Garbage Collection in Jconsole ...
> On the Network Server in the console from where the Network Server was started lot of messages are printed ... Unloading XXX classes ...
> Can these messages be directed to the derby.log file?
> I think they should be so that it would be easier to analyze rather than read on the screen.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)