db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (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:09:44 GMT
    [ http://issues.apache.org/jira/browse/DERBY-444?page=comments#action_12368805 ] 

Bryan Pendleton commented on DERBY-444:

I'm not sure I'm following the basic thrust of this. Is there something special about the
Connection object? Couldn't we just as easily happen to run out of memory when creating a
Statement, or a ResultSet, or at various other places where the app calls into Derby to perform
some work?

Would every class in the external API need be changed similarly to how you changed EmbedConnection
and InternalDriver?



> 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