db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3612) Developer's Guide needs correction on garbage collection
Date Fri, 11 Apr 2008 18:22:06 GMT

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

Kim Haase updated DERBY-3612:

    Attachment: tdevdvlp20349.html

Attaching DERBY-3612.diff and tdevdvlp20349.html. This patch 

 - corrects the description of System.gc() to make clear that it requests but does not force
garbage collection

 - removes the references to the -nogc and -noclassgc options, since these appear to have
been obsolete since Java 2 came in, and replaces them with the current non-standard -Xnoclassgc

 - tidies up the language a bit (changes passive voice to active, etc.)

I'd be grateful if someone could check the correctness of the modified info. If I don't hear
in a week or so, though, I'll go ahead and commit this.

> Developer's Guide needs correction on garbage collection
> --------------------------------------------------------
>                 Key: DERBY-3612
>                 URL: https://issues.apache.org/jira/browse/DERBY-3612
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-3612.diff, tdevdvlp20349.html
> In a comment on DERBY-3585, Martin Zaun pointed out the following error:
> devguide/tdevdvlp20349.dita
>    - found a flatly wrong statement but did NOT correct here since
>      unrelated to server shutdown authentication:
>      "You cannot explicitly request that the JVM unload a class, but you
>      can ensure that the EmbeddedDriver class is unloaded by using a
>      System.gc() to force it to garbage collect classes that are no longer
>      needed. Running with -nogc or -noclassgc definitely prevents the class
>      from being unloaded and makes you unable to restart Derby in the same
>      JVM."
>      System.gc() is only a suggestion to the Runtime to garbage-collect, it
>      cannot be enforced, and there's no guarantee whatsoever that GC has
>      run and any classes been unloaded. Likewise it's most probably not
>      guarantueed that -nogc or -noclassgc definitely (!) prevent a class
>      from being unloaded (a JVM may ignore these options...) 
> This needs to be fixed. Thanks, Martin.
> One more question: are -nogc and -noclassgc java command line options, or options to
some other command? I can't find them in the java command documentation -- http://java.sun.com/javase/6/docs/technotes/tools/windows/java.html.
There is an -Xnoclassgc option, however.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message