You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "John Sisson (JIRA)" <de...@geronimo.apache.org> on 2004/11/08 01:41:33 UTC
[jira] Created: (GERONIMO-453) DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
---------------------------------------------------------------------------------------------------
Key: GERONIMO-453
URL: http://nagoya.apache.org/jira/browse/GERONIMO-453
Project: Apache Geronimo
Type: Bug
Reporter: John Sisson
The Derby doco in the section "Shutting Down the System" at http://incubator.apache.org/derby/manuals/develop/develop12.html says the following:
Typically, an application using an embedded Derby engine shuts down Derby just before shutting itself down.
However, an application can shut down Derby and later restart it in the same JVM session.
To restart Derby successfully, the JVM needs to unload org.apache.derby.jdbc.EmbeddedDriver,
so that it can reload it when it restarts Derby. (Loading the local driver starts Derby.)
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.
Anyone have any objections to the recommendation of calling System.gc()?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-453) DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-453?page=all ]
Aaron Mulder updated GERONIMO-453:
----------------------------------
Fix Version: 1.0-M5
Description:
The Derby doco in the section "Shutting Down the System" at http://incubator.apache.org/derby/manuals/develop/develop12.html says the following:
Typically, an application using an embedded Derby engine shuts down Derby just before shutting itself down.
However, an application can shut down Derby and later restart it in the same JVM session.
To restart Derby successfully, the JVM needs to unload org.apache.derby.jdbc.EmbeddedDriver,
so that it can reload it when it restarts Derby. (Loading the local driver starts Derby.)
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.
Anyone have any objections to the recommendation of calling System.gc()?
was:
The Derby doco in the section "Shutting Down the System" at http://incubator.apache.org/derby/manuals/develop/develop12.html says the following:
Typically, an application using an embedded Derby engine shuts down Derby just before shutting itself down.
However, an application can shut down Derby and later restart it in the same JVM session.
To restart Derby successfully, the JVM needs to unload org.apache.derby.jdbc.EmbeddedDriver,
so that it can reload it when it restarts Derby. (Loading the local driver starts Derby.)
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.
Anyone have any objections to the recommendation of calling System.gc()?
Version: 1.0-M4
Environment:
Are you suggesting we call System.gc() in the doStop of the DerbySystemGBean?
> DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
> ---------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-453
> URL: http://issues.apache.org/jira/browse/GERONIMO-453
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M4
> Reporter: John Sisson
> Assignee: John Sisson
> Fix For: 1.0-M5
>
> The Derby doco in the section "Shutting Down the System" at http://incubator.apache.org/derby/manuals/develop/develop12.html says the following:
> Typically, an application using an embedded Derby engine shuts down Derby just before shutting itself down.
> However, an application can shut down Derby and later restart it in the same JVM session.
> To restart Derby successfully, the JVM needs to unload org.apache.derby.jdbc.EmbeddedDriver,
> so that it can reload it when it restarts Derby. (Loading the local driver starts Derby.)
> 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.
> Anyone have any objections to the recommendation of calling System.gc()?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-453) DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-453?page=all ]
Matt Hogstrom closed GERONIMO-453:
----------------------------------
Transmitting file data .
Committed revision 332384.
> DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
> ---------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-453
> URL: http://issues.apache.org/jira/browse/GERONIMO-453
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M4
> Reporter: John Sisson
> Assignee: Matt Hogstrom
> Fix For: 1.0
>
> The Derby doco in the section "Shutting Down the System" at http://incubator.apache.org/derby/manuals/develop/develop12.html says the following:
> Typically, an application using an embedded Derby engine shuts down Derby just before shutting itself down.
> However, an application can shut down Derby and later restart it in the same JVM session.
> To restart Derby successfully, the JVM needs to unload org.apache.derby.jdbc.EmbeddedDriver,
> so that it can reload it when it restarts Derby. (Loading the local driver starts Derby.)
> 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.
> Anyone have any objections to the recommendation of calling System.gc()?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-453) DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-453?page=all ]
Matt Hogstrom resolved GERONIMO-453:
------------------------------------
Resolution: Fixed
Added System.gc()
Index: src/java/org/apache/geronimo/derby/DerbySystemGBean.java
===================================================================
--- src/java/org/apache/geronimo/derby/DerbySystemGBean.java (revision 332238)
+++ src/java/org/apache/geronimo/derby/DerbySystemGBean.java (working copy)
@@ -69,6 +69,7 @@
} catch (SQLException e) {
// SQLException gets thrown on successful shutdown so ignore
}
+ System.gc(); // Added as documented in Derby Documentation
log.info("Stopped");
}
@@ -78,6 +79,7 @@
} catch (SQLException e) {
// SQLException gets thrown on successful shutdown so ignore
}
+ System.gc(); // Added as documented in Derby Documentation
log.info("Failed");
}
> DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
> ---------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-453
> URL: http://issues.apache.org/jira/browse/GERONIMO-453
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M4
> Reporter: John Sisson
> Assignee: Matt Hogstrom
> Fix For: 1.0
>
> The Derby doco in the section "Shutting Down the System" at http://incubator.apache.org/derby/manuals/develop/develop12.html says the following:
> Typically, an application using an embedded Derby engine shuts down Derby just before shutting itself down.
> However, an application can shut down Derby and later restart it in the same JVM session.
> To restart Derby successfully, the JVM needs to unload org.apache.derby.jdbc.EmbeddedDriver,
> so that it can reload it when it restarts Derby. (Loading the local driver starts Derby.)
> 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.
> Anyone have any objections to the recommendation of calling System.gc()?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-453) DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-453?page=all ]
John Sisson reassigned GERONIMO-453:
------------------------------------
Assign To: John Sisson
> DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
> ---------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-453
> URL: http://issues.apache.org/jira/browse/GERONIMO-453
> Project: Geronimo
> Type: Bug
> Reporter: John Sisson
> Assignee: John Sisson
>
> The Derby doco in the section "Shutting Down the System" at http://incubator.apache.org/derby/manuals/develop/develop12.html says the following:
> Typically, an application using an embedded Derby engine shuts down Derby just before shutting itself down.
> However, an application can shut down Derby and later restart it in the same JVM session.
> To restart Derby successfully, the JVM needs to unload org.apache.derby.jdbc.EmbeddedDriver,
> so that it can reload it when it restarts Derby. (Loading the local driver starts Derby.)
> 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.
> Anyone have any objections to the recommendation of calling System.gc()?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-453) DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
Posted by "David Blevins (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-453?page=all ]
David Blevins updated GERONIMO-453:
-----------------------------------
Fix Version: 1.0
(was: 1.0-M5)
> DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
> ---------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-453
> URL: http://issues.apache.org/jira/browse/GERONIMO-453
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M4
> Reporter: John Sisson
> Assignee: John Sisson
> Fix For: 1.0
>
> The Derby doco in the section "Shutting Down the System" at http://incubator.apache.org/derby/manuals/develop/develop12.html says the following:
> Typically, an application using an embedded Derby engine shuts down Derby just before shutting itself down.
> However, an application can shut down Derby and later restart it in the same JVM session.
> To restart Derby successfully, the JVM needs to unload org.apache.derby.jdbc.EmbeddedDriver,
> so that it can reload it when it restarts Derby. (Loading the local driver starts Derby.)
> 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.
> Anyone have any objections to the recommendation of calling System.gc()?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-453) DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-453?page=all ]
Matt Hogstrom reassigned GERONIMO-453:
--------------------------------------
Assign To: Matt Hogstrom (was: John Sisson)
> DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as recommended in the Derby doco
> ---------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-453
> URL: http://issues.apache.org/jira/browse/GERONIMO-453
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M4
> Reporter: John Sisson
> Assignee: Matt Hogstrom
> Fix For: 1.0
>
> The Derby doco in the section "Shutting Down the System" at http://incubator.apache.org/derby/manuals/develop/develop12.html says the following:
> Typically, an application using an embedded Derby engine shuts down Derby just before shutting itself down.
> However, an application can shut down Derby and later restart it in the same JVM session.
> To restart Derby successfully, the JVM needs to unload org.apache.derby.jdbc.EmbeddedDriver,
> so that it can reload it when it restarts Derby. (Loading the local driver starts Derby.)
> 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.
> Anyone have any objections to the recommendation of calling System.gc()?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira