You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2006/06/06 01:11:32 UTC
[Db-derby Wiki] Update of "HighValueFixCandidates" by DavidVanCouvering
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.
The following page has been changed by DavidVanCouvering:
http://wiki.apache.org/db-derby/HighValueFixCandidates
------------------------------------------------------------------------------
== High Value 10.1 Branch Bug Fixing Candidates ==
These are issues that would be great to see fixed in the maintenance branch. Once fixed in the trunk, an assessment should be made of whether they are appropriate for port to 10.1.
|| JIRA_ISSUE || SUMMARY || COMMENTS||
- ||[http://issues.apache.org/jira/browse/DERBY-1069 DERBY-1069]||Client should unwrap exceptions thrown in privilege blocks. || We could avoid lots of user questions generated by client messages like: "java.security.PrivilegedActionException : Error opening socket to server xx on port 1527 with message : null". Just not very helpful||
||[http://issues.apache.org/jira/browse/DERBY-1004 DERBY-1004]|| Client should not require user to rollback the active transaction before call to PooledConnection.getConnection()|| ||
||[http://issues.apache.org/jira/browse/DERBY-1018 DERBY-1018]|| Client xa Statement.getConnection and DatabaseMetadata.getConnection returns underlying NetXAConnection instead of Logical connection|| ||
||[http://issues.apache.org/jira/browse/DERBY-1020 DERBY-1020]|| Network Server treats errors on cleanup of connections as an unexpected error after intentional shutdown of the database/server|| ||