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 "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2006/02/19 08:01:25 UTC

[jira] Created: (DERBY-1011) Improve Network Server Exception Handling

Improve Network Server Exception Handling
-----------------------------------------

         Key: DERBY-1011
         URL: http://issues.apache.org/jira/browse/DERBY-1011
     Project: Derby
        Type: Improvement
  Components: Network Server  
    Versions: 10.2.0.0    
    Reporter: Kathey Marsden


I think that there needs to be a comprehensive look at the  Network Server exception handling,  which is an ongoing area of concern.  I am not sure how much can be done from a DRDA perspective but it would definitely be worth a look.

    -  Exceptions are localized with a stored procedure call which is problematic when the procedure can't be called because of a serious error and traditionally has caused other issues as well.  It seems like somehow we could negotiate the client locale up front and send back the localized message 
    - Multiple exceptions are  flattenned into one and there is limitted space to send parameter info to the client.  (70 characters according to DRDA).  
    - Many warnings do not get returned to the client.
    - I think SQLExceptions thrown by the Network Server are not getting logged to derby.log 
   



-- 
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