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 "Knut Anders Hatlen (JIRA)" <de...@db.apache.org> on 2006/01/19 17:28:43 UTC
[jira] Updated: (DERBY-23) just booting jdbc driver and shutting
down seem to leak memory
[ http://issues.apache.org/jira/browse/DERBY-23?page=all ]
Knut Anders Hatlen updated DERBY-23:
------------------------------------
Attachment: DERBY-23-npe.diff
DERBY-23-npe.stat
derbyall_report.txt
I have attached a patch (DERBY-23-npe.diff) that addresses the
NullPointerException messages from rawStoreDaemon threads we have seen
in derbyall on some occasions.
The NullPointerExceptions are thrown because
ContextService.threadContextList is set to null in
ContextService.stop(), but some of the daemon threads might still try
to access the variable. The patch adds checks for threadContextList
being null, and returns null or false in those cases instead of
failing with a NullPointerException.
Five tests in derbyall failed when this patch was applied, but that
seems to be what one should expect these days. All of the failures are
also seen in the daily regression tests.
Feel free to review and comment on the patch. Thanks.
> just booting jdbc driver and shutting down seem to leak memory
> --------------------------------------------------------------
>
> Key: DERBY-23
> URL: http://issues.apache.org/jira/browse/DERBY-23
> Project: Derby
> Type: Bug
> Components: Services
> Versions: 10.0.2.0
> Reporter: Tulika Agrawal
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: DERBY-23-npe.diff, DERBY-23-npe.stat, DERBY-23-with_comments.diff, DERBY-23.diff, DERBY-23.stat, derbyall_report.txt
>
> Reporting for Daniel John Debrunner.
> Doing simple boot and shutdown of the driver in a loop
> seem to grow the heap forever:
> new org.apache.derby.jdbc.EmbeddedDriver(); //boot the driver
> DriverManager.getConnection("jdbc:derby:;shutdown=true");
> //shutdown the cloudscape instance completely
> after booting and shutting down 1516 times, memory used is
> ~~41931056 bytes.
> Sample GC Output:
> 1931.93: [Full GC 43484K->43243K(65088K), 0.1779751 secs]
> 1933.13: [Full GC 43511K->43270K(65088K), 0.1914383 secs]
> 1934.47: [Full GC 43538K->43297K(65088K), 0.1808878 secs]
> 1935.68: [Full GC 43564K->43324K(65088K), 0.4461623 secs]
> 1937.43: [Full GC 43591K->43350K(65088K), 0.1842980 secs]
> 1938.63: [Full GC 43617K->43377K(65088K), 0.1873431 secs]
> 1939.85: [Full GC 43644K->43404K(65088K), 0.1948505 secs]
> 1941.07: [Full GC 43671K->43430K(65088K), 0.1790895 secs]
--
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
Re: [jira] Updated: (DERBY-23) just booting jdbc driver and shutting
down seem to leak memory
Posted by "Bernt M. Johnsen" <Be...@Sun.COM>.
Reviewing and testing for commit now.
>>>>>>>>>>>> Knut Anders Hatlen (JIRA) wrote (2006-01-19 17:28:43):
> [ http://issues.apache.org/jira/browse/DERBY-23?page=all ]
>
> Knut Anders Hatlen updated DERBY-23:
> ------------------------------------
>
> Attachment: DERBY-23-npe.diff
> DERBY-23-npe.stat
> derbyall_report.txt
>
> I have attached a patch (DERBY-23-npe.diff) that addresses the
> NullPointerException messages from rawStoreDaemon threads we have seen
> in derbyall on some occasions.
>
> The NullPointerExceptions are thrown because
> ContextService.threadContextList is set to null in
> ContextService.stop(), but some of the daemon threads might still try
> to access the variable. The patch adds checks for threadContextList
> being null, and returns null or false in those cases instead of
> failing with a NullPointerException.
>
> Five tests in derbyall failed when this patch was applied, but that
> seems to be what one should expect these days. All of the failures are
> also seen in the daily regression tests.
>
> Feel free to review and comment on the patch. Thanks.
>
> > just booting jdbc driver and shutting down seem to leak memory
> > --------------------------------------------------------------
> >
> > Key: DERBY-23
> > URL: http://issues.apache.org/jira/browse/DERBY-23
> > Project: Derby
> > Type: Bug
> > Components: Services
> > Versions: 10.0.2.0
> > Reporter: Tulika Agrawal
> > Assignee: Knut Anders Hatlen
> > Priority: Minor
> > Fix For: 10.2.0.0
> > Attachments: DERBY-23-npe.diff, DERBY-23-npe.stat, DERBY-23-with_comments.diff, DERBY-23.diff, DERBY-23.stat, derbyall_report.txt
> >
> > Reporting for Daniel John Debrunner.
> > Doing simple boot and shutdown of the driver in a loop
> > seem to grow the heap forever:
> > new org.apache.derby.jdbc.EmbeddedDriver(); //boot the driver
> > DriverManager.getConnection("jdbc:derby:;shutdown=true");
> > //shutdown the cloudscape instance completely
> > after booting and shutting down 1516 times, memory used is
> > ~~41931056 bytes.
> > Sample GC Output:
> > 1931.93: [Full GC 43484K->43243K(65088K), 0.1779751 secs]
> > 1933.13: [Full GC 43511K->43270K(65088K), 0.1914383 secs]
> > 1934.47: [Full GC 43538K->43297K(65088K), 0.1808878 secs]
> > 1935.68: [Full GC 43564K->43324K(65088K), 0.4461623 secs]
> > 1937.43: [Full GC 43591K->43350K(65088K), 0.1842980 secs]
> > 1938.63: [Full GC 43617K->43377K(65088K), 0.1873431 secs]
> > 1939.85: [Full GC 43644K->43404K(65088K), 0.1948505 secs]
> > 1941.07: [Full GC 43671K->43430K(65088K), 0.1790895 secs]
>
> --
> 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
>
--
Bernt Marius Johnsen, Database Technology Group,
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway