db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-444) Handle OutOfMemoryError exceptions when creating a new embedded connection
Date Fri, 03 Mar 2006 22:43:42 GMT
    [ http://issues.apache.org/jira/browse/DERBY-444?page=comments#action_12368811 ] 

Daniel John Debrunner commented on DERBY-444:

This is a sub-task of 

Make Derby engine robust in case of OutOfMemoryError exceptions  (DERBY-443)

So, yes, one would need to do other changes in other areas, I'm just starting off in one well
contained area as a way to
see what is possible and to see if I can provide some form of initial framework/useful code.
Incremental development,
get something simple working quickly and build from there, rather than trying to solve everything

I do think something needs to be done in this area (DERBY-443), there is the person on derby-user
that put the cache-size up
to 10,,000 pages and may be hitting OutOfMemoryErrors, wouldn't it be better if Derby just
didn't shutdown with his
configuration, instead kept runing after it saw an OOME with a smaller cache. This specific
patch/Jira issue doesn't get us there
but I'm trying to make a start. I just chose to start with connections.

> Handle OutOfMemoryError exceptions when creating a new embedded connection
> --------------------------------------------------------------------------
>          Key: DERBY-444
>          URL: http://issues.apache.org/jira/browse/DERBY-444
>      Project: Derby
>         Type: Sub-task
>   Components: JDBC
>     Reporter: Daniel John Debrunner
>     Assignee: Daniel John Debrunner
>  Attachments: derby444_draft_v1.txt
> If an OutOfMemoryError is thrown while creating objects for a new embedded connection,
reject the connection request with a SQLException and do not shutdown the system.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message